From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: "Jean-François Stenuit" <jfs@keytradebank.com>,
"Keith Mannthey" <kmannth@gmail.com>, "0602@eq.cz" <0602@eq.cz>,
Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: totally random "VFS: Cannot open root device"
Date: Thu, 01 Dec 2005 20:53:40 -0500 [thread overview]
Message-ID: <438FA924.1090005@pobox.com> (raw)
In-Reply-To: <438EFAA5.3070901@gmail.com>
Tejun Heo wrote:
> Jean-François Stenuit wrote:
>
>> Hi Tejun,
>>
>> Thanks for taking the time to check.
>>
>> Output of your trace with ata_piix.override_PCS=0
>> 1st boot : success : combined=0 orig_mask=0x11
>> 2nd boot : success : combined=0 orig_mask=0x11
>> 3rd boot : failure : combined=0 orig_mask=0x0
>> 4th boot : failure : combined=0 orig_mask=0x0
>> 5th boot : failure : combined=0 orig_mask=0x0
>> 6th boot : failure : combined=0 orig_mask=0x0
>> 7th boot : success : combined=0 orig_mask=0x11
>> Output of your trace with ata_piix.override_PCS=1
>> 1st boot : success : combined=0 orig_mask=0x0
>> 2nd boot : success : combined=0 orig_mask=0x0
>> 3rd boot : success : combined=0 orig_mask=0x0
>> 4th boot : success : combined=0 orig_mask=0x0
>> 5th boot : success : combined=0 orig_mask=0x0
>> 6th boot : success : combined=0 orig_mask=0x0
>> 7th boot : success : combined=0 orig_mask=0x0
>> 8th boot : success : combined=0 orig_mask=0x0
>>
>> Looks like you have found a fix/workaround for this bug (but it still
>> does not give the reason why it's failing).
>>
>
> It probably is a BIOS issue. The weird thing though is that the port
> works fine with its corresponding ENABLED bit cleared. Anyways, if it
> works by ignoring the ENABLED bit, ignoring should just be fine.
>
> 0602, can you verify this workaround works on your machine too?
>
> Jeff (Hi!), if 0602 also confirms that this workaround works, I'll
> submit a patch to make ata_piix ignore PCS values on ICH5's. How does
> that sound to you?
I am being dragged into this thread with little background info. Here's
some data points that may be relevant:
* until very recently, ata_piix's definitions for the ENABLED and
PRESENT bits was reversed.
* the PRESENT bit reflects a device present status just like the SStatus
phy register does. This implies that one must wait, before assuming
that the PRESENT bit's absence truly indicates absence of a device.
* the device may be in various power management states. It may be wise
to issue COMRESET by
- clear ENABLED bit
- set ENABLED bit
- wait for device to appear
- if no device appeared, clear ENABLED bit
In sum, think about the underlying SATA phy registers, and how they
logically map to the PCS bits.
Jeff
next prev parent reply other threads:[~2005-12-02 1:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <438B6E05.8070009@eq.cz>
2005-11-30 4:35 ` totally random "VFS: Cannot open root device" Tejun Heo
2005-11-30 9:05 ` Jean-François Stenuit
2005-11-30 16:30 ` Randy.Dunlap
2005-12-01 9:42 ` Jean-François Stenuit
2005-12-01 11:20 ` Jean-François Stenuit
2005-11-30 13:07 ` 0602
2005-11-30 22:05 ` Keith Mannthey
2005-12-01 9:40 ` Jean-François Stenuit
2005-12-01 11:20 ` Tejun Heo
2005-12-01 12:59 ` Jean-François Stenuit
2005-12-01 13:29 ` Tejun Heo
2005-12-01 15:34 ` 0602
2005-12-02 1:53 ` Jeff Garzik [this message]
2005-12-02 3:00 ` Tejun Heo
2005-12-02 3:26 ` [PATCH] ata_piix: ignore all zero PCS value on ICH5's Tejun Heo
2005-12-02 12:40 ` 0602
2005-12-05 10:07 ` Jean-François Stenuit
2005-12-05 10:17 ` Tejun Heo
2006-01-29 5:22 ` Jeff Garzik
2006-02-01 2:01 ` Tejun Heo
2006-02-09 9:23 ` Jeff Garzik
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=438FA924.1090005@pobox.com \
--to=jgarzik@pobox.com \
--cc=0602@eq.cz \
--cc=htejun@gmail.com \
--cc=jfs@keytradebank.com \
--cc=kmannth@gmail.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).