* Maybe a corrupted BIOS?
@ 2006-06-12 4:45 zhao, forrest
2006-06-12 5:14 ` Tejun Heo
2006-06-12 6:58 ` Jeff Garzik
0 siblings, 2 replies; 3+ messages in thread
From: zhao, forrest @ 2006-06-12 4:45 UTC (permalink / raw)
To: jeff; +Cc: linux-ide
Hi, Jeff
I encountered a tricky problem. Let me described it from start.
This morning I applied the "AHCI suspend/resume" patch against latest
#upstream without much modification, then after a round of suspend/
resume, then system can't boot from AHCI mode, also can't boot from
"enhanced mode with AHCI disabled". But it can boot from "compatible
mode" with ata_piix driver to drive the hardware.
So now I'm totally clueless about how to make AHCI mode come back to
life. It seems that I need to trigger a low-level re-initialization of
SATA controller. Have you ever met such weird behavior before?
Thanks,
Forrest
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Maybe a corrupted BIOS?
2006-06-12 4:45 Maybe a corrupted BIOS? zhao, forrest
@ 2006-06-12 5:14 ` Tejun Heo
2006-06-12 6:58 ` Jeff Garzik
1 sibling, 0 replies; 3+ messages in thread
From: Tejun Heo @ 2006-06-12 5:14 UTC (permalink / raw)
To: zhao, forrest; +Cc: jeff, linux-ide
zhao, forrest wrote:
> Hi, Jeff
>
> I encountered a tricky problem. Let me described it from start.
>
> This morning I applied the "AHCI suspend/resume" patch against latest
> #upstream without much modification, then after a round of suspend/
> resume, then system can't boot from AHCI mode, also can't boot from
> "enhanced mode with AHCI disabled". But it can boot from "compatible
> mode" with ata_piix driver to drive the hardware.
>
> So now I'm totally clueless about how to make AHCI mode come back to
> life. It seems that I need to trigger a low-level re-initialization of
> SATA controller. Have you ever met such weird behavior before?
Remove power, wait for a while, and re-apply power. Resume failure from
memsleep puts my p5ld2 in a pretty weird state (POSTing hangs).
Removing power helps in my case.
--
tejun
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Maybe a corrupted BIOS?
2006-06-12 4:45 Maybe a corrupted BIOS? zhao, forrest
2006-06-12 5:14 ` Tejun Heo
@ 2006-06-12 6:58 ` Jeff Garzik
1 sibling, 0 replies; 3+ messages in thread
From: Jeff Garzik @ 2006-06-12 6:58 UTC (permalink / raw)
To: zhao, forrest; +Cc: linux-ide
zhao, forrest wrote:
> Hi, Jeff
>
> I encountered a tricky problem. Let me described it from start.
>
> This morning I applied the "AHCI suspend/resume" patch against latest
> #upstream without much modification, then after a round of suspend/
> resume, then system can't boot from AHCI mode, also can't boot from
> "enhanced mode with AHCI disabled". But it can boot from "compatible
> mode" with ata_piix driver to drive the hardware.
>
> So now I'm totally clueless about how to make AHCI mode come back to
> life. It seems that I need to trigger a low-level re-initialization of
> SATA controller. Have you ever met such weird behavior before?
I've seen things like this...
* sometimes testing can lead to a loss of BIOS NVRAM. Running BIOS's
'restore to defaults' usually fixes this.
* sometimes testing can fry your BIOS battery, or the battery may just
die. get a new battery.
* sometimes the hardware just "needs a breather", like Tejun described.
Power off the machine, unplug it, unplug the ethernet cable, and let
it sit for a little while.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-06-12 6:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-12 4:45 Maybe a corrupted BIOS? zhao, forrest
2006-06-12 5:14 ` Tejun Heo
2006-06-12 6:58 ` Jeff Garzik
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).