cached PCS
can you resurrect your cached PCS patch?
2.6.18-rc didn't fix the ghost device and long boot delay problems for everybody.
Quoted 3 lines · Jeff Garzik
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?
Signature · 1 line
tejun
Quoted 6 lines · Tejun Heo
Quoted 3 lines · Jeff Garzik
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?
Jeff
Quoted 9 lines · Jeff Garzik
Quoted 6 lines · Tejun Heo
Quoted 3 lines · Jeff Garzik
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.
Signature · 1 line
tejun
Quoted 5 lines · Tejun Heo
Quoted 4 lines · Jeff Garzik
Quoted 3 lines · Tejun Heo
Quoted 2 lines · Jeff Garzik
can you resurrect your cached PCS patch?
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
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
Jeff
Quoted 10 lines · Jeff Garzik
Quoted 9 lines · Tejun Heo
Quoted 8 lines · Jeff Garzik
Quoted 6 lines · Tejun Heo
Quoted 3 lines · Jeff Garzik
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?
Quoted 8 lines
Quoted 3 lines
Quoted 1 line
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?
Thanks.
Signature · 1 line
tejun
Quoted 22 lines · Tejun Heo
Quoted 10 lines · Jeff Garzik
Quoted 9 lines · Tejun Heo
Quoted 8 lines · Jeff Garzik
Quoted 6 lines · Tejun Heo
Quoted 3 lines · Jeff Garzik
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?
Quoted 8 lines
Quoted 3 lines
Quoted 1 line
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=2I was talking about bugzilla bug #6724.
Quoted 7 lines
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 toprereset()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.
Jeff
Quoted 29 lines · Jeff Garzik
Quoted 28 lines · Tejun Heo
Quoted 10 lines · Jeff Garzik
Quoted 9 lines · Tejun Heo
Quoted 8 lines · Jeff Garzik
Quoted 6 lines · Tejun Heo
Quoted 3 lines · Jeff Garzik
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?
Quoted 8 lines
Quoted 3 lines
Quoted 1 line
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=2I 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 toprereset()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.
Quoted 7 lines
Quoted 1 line
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/idedmesg 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?
Signature · 1 line
tejun
Quoted 6 lines · Tejun Heo
Quoted 1 line
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_PCSfor 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 setIGNORE_PCSand 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.
Signature · 1 line
tejun