David Brownell wrote:
However, it's also confusing that the bug doesn't match the downstream
bug that allegedly corresponds to this. In particular, this report
claims the issue appears with 2.6.14-rc4, and the downstream bug
describes older kernels _without_ a patch that addresses a similar
bug that also "hangs at this point".
Are we sure the bug report is really against 2.6.14-rc4? That seems
oddly fast for a bug to get through the Gentoo bug database and then
get bounced up to the osdl database ...
I assume you meant 2.6.16-rc4 rather than 2.6.14-rc4.
I'll try and clarify what has gone on on the downstream bug
(http://bugs.gentoo.org/122277) from the top:
- The user ran 2.6.14 (and older kernels) without problem.
- 2.6.15 came out, and the user upgraded through the package system.
- 2.6.15 introduced this problem where it would hang during bootup on
most warm boots. It looks like this happened because early handoff was
enabled by default in 2.6.15 whereas it was not in 2.6.14, although the
exact cause of the problem was not known at this point. The user filed
the bug report at http://bugs.gentoo.org/12227 and you can see the point
of the hang in comment #2.
- You then reworked the EHCI early handoff in the 2.6.16-rc tree based
on feedback from others. This didn't solve the problem. See comment #4.
At this point the user was running 2.6.16-rc2 and the point of the hang
changed to a message about the io scheduler, but it became clearer later
that the hang actually occurs within the usb pci-quirks file.
- You then disabled the SMI control code in the EHCI handoff. This
didn't solve the problem. See comment #9. (There is no feedback shown on
the bug as we discussed this on IRC).
- I posted a comment at http://bugzilla.kernel.org/show_bug.cgi?id=6011#c17
describing the situation and Alan Stern gave some pointers towards
diagnosing it.
- I created 2 patches (comment #12 and comment #15) which narrowed down
the exact function call which was causing the hang. At this point, the
user was testing 2.6.16-rc4 and applying my patch on top.
- Not really knowing what to do next, I filed the bug report found at
http://bugzilla.kernel.org/show_bug.cgi?id=6098
As for speed, Gentoo immediately include every non-rc kernel release in
the testing tree (which is very popular), and typically move those
releases into the stable tree 2-3 weeks later.
If a bug is reported and a fix is not obvious we ask the user to
reproduce it on the latest development kernel (in this case 2.6.16-rc4)
and then file bugs at the kernel bugzilla. This is the kind of process
that has happened here.
I guess I may have confused you by making you think the bug was
*introduced* in 2.6.16-rc4? If so, I apologise: it probably existed in
2.6.14 and older if the handoff parameter was used. I was just following
the usual procedure of making sure the problem hasn't been fixed in the
latest bleeding edge kernel before troubling you with it. I'll be
clearer in future :)
Daniel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
