From: Jeff Garzik <jeff@garzik.org>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Maybe a corrupted BIOS?
Date: Mon, 12 Jun 2006 02:58:56 -0400 [thread overview]
Message-ID: <448D10B0.5000703@garzik.org> (raw)
In-Reply-To: <1150087543.5721.49.camel@forrest26.sh.intel.com>
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.
prev parent reply other threads:[~2006-06-12 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=448D10B0.5000703@garzik.org \
--to=jeff@garzik.org \
--cc=forrest.zhao@intel.com \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).