From: Tejun Heo <htejun@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Keith Owens <kaos@ocs.com.au>,
stevenm@umd.edu
Subject: Re: cached PCS
Date: Thu, 10 Aug 2006 13:50:25 +0900 [thread overview]
Message-ID: <44DABB11.5020707@gmail.com> (raw)
In-Reply-To: <44D9C31B.6000901@gmail.com>
Tejun Heo wrote:
>> Did you look at some of the other messages? He provided some debug
>> traces in follow-up messages.
>
> Yes, I have and I can't think of any other way than ignoring PCS to work
> around the problem. If we set IGNORE_PCS for ich5 sata then we can also
> forget about cached PCS which is for ich5 sata. But, we might see ghost
> device detection and accompanying long delays.
>
> For ich 6/7/8, your recent change and honor-pcs patch should do the job.
> For ICH5, well... Just set IGNORE_PCS and wait for bug reports?
[CC'ing Steve (the bug reporter of #6724), Hi!]
Steve just reported -rc4 doesn't fix the problem && he saw complete
misdetection of *all* devices on soft reboots. I think Steve and Keith
are experiencing the same problem here.
PCS enabled bits are cleared at some point and cached PCS works around
the problem by caching the bits early but for soft reboots it doesn't do
any good. One interesting thing is that BIOSen seem to recognize the
drives fine (right?) on such reboots even though PCS enabled bits would
be zero. FWIW, IGNORE_PCS works fine for Steve.
Thanks.
--
tejun
prev parent reply other threads:[~2006-08-10 4:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 6:21 cached PCS Jeff Garzik
2006-08-09 9:48 ` Tejun Heo
2006-08-09 10:08 ` Jeff Garzik
2006-08-09 10:11 ` Tejun Heo
2006-08-09 10:27 ` Jeff Garzik
2006-08-09 10:39 ` Tejun Heo
2006-08-09 10:46 ` Jeff Garzik
2006-08-09 11:12 ` Tejun Heo
2006-08-10 4:50 ` Tejun Heo [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=44DABB11.5020707@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=kaos@ocs.com.au \
--cc=linux-ide@vger.kernel.org \
--cc=stevenm@umd.edu \
/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).