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.
-
: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html