All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Keith Owens <kaos@ocs.com.au>
Subject: Re: cached PCS
Date: Wed, 09 Aug 2006 20:12:27 +0900	[thread overview]
Message-ID: <44D9C31B.6000901@gmail.com> (raw)
In-Reply-To: <44D9BD06.5080103@garzik.org>

Jeff Garzik wrote:
> Tejun Heo wrote:
>> Jeff Garzik wrote:
>>> Tejun Heo wrote:
>>>> Jeff Garzik wrote:
>>>>> Tejun Heo wrote:
>>>>>> Jeff Garzik wrote:
>>>>>>> can you resurrect your cached PCS patch?
>>>>>>>
>>>>>>> 2.6.18-rc didn't fix the ghost device and long boot delay 
>>>>>>> problems for everybody.
>>>>>>
>>>>>> The cached PCS patch was to fix device detection failure on some 
>>>>>> ICH5s where PCS is cleared while probing the first port.  
>>>>>> Remaining ghost device and long boot delay are fixed by honor-PCS 
>>>>>> patch.  Do you want me to resurrect both?
>>>>>
>>>>> hrm.  Maybe just honor-PCS?
>>>>
>>>> Yeap, we need to verify whether the less-jealous-PCS-update patch 
>>>> cured the ICH5 problem.
>>>
>>> If you are talking about the patch currently in 2.6.18-rc, I got 
>>> several ACKs that it fixed their problems.
>>>
>>> But OTOH, there was also
>>> http://marc.theaimsgroup.com/?t=115346292700002&r=1&w=2
>>
>> I was talking about bugzilla bug #6724.
>>
>> http://bugzilla.kernel.org/show_bug.cgi?id=6724
>>
>> It was a weird case of ICH5 clearing PCS present bits while the first 
>> port is being probed.  The clearing happens during actual probe, that 
>> is, the bits look okay till the end of the first prereset() but on 
>> entry to prereset() for the second port, enabled bits are gone.  IIRC, 
>> bug#6724 is different from all other reports.
>>
>> I asked the reporter to test 2.6.18-rc4 and see whether the problem is 
>> gone with new PCS handling.  I'm a bit skeptical about the result.  If 
>> the problem remains with 2.6.18-rc4, we'll need that cached PCS to 
>> solve that particular case.
>>
>> BTW, do you know what Keith Owen's chipset was?
> 
> (Keith CC'd)
> 
> I didn't see lspci output, but it looks like ICH5 from his drivers/ide 
> dmesg output.
> 
> 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?

-- 
tejun

  reply	other threads:[~2006-08-09 11:12 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 [this message]
2006-08-10  4:50               ` Tejun Heo

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=44D9C31B.6000901@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kaos@ocs.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.