Bug 181732
Summary: | 4-port usb hub not working as expected with rawhide kernels.. works under latest fc4 kernel | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jef Spaleta <jspaleta> |
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | davej, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.6.18-1.2200.fc5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-21 21:38:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Jef Spaleta
2006-02-16 01:19:03 UTC
Wild! Jef, would do this for me... plug this thing in on broken kernel, plug the storage, then take a dmesg > /tmp/dmesg.bad. Then, do the same on working kernel (as close sequence as possible), and dmesg > /tmp/dmesg.good. Then attach both dmesgs to the bug, unedited. It would be best if this was done on the same box, to exclude the HC issues. The objective is to have a meaningful run of diff -u dmesg.good dmesg.bad I'm asking about unedited dmesg because the problem may be in HC initialization, handoff, TT (transaction translator), or other thing way above the failure. Done... good kernel kernel-2.6.15-1.1831_FC4 bad kernel kernel-2.6.15-1.1948_FC5 run on exactly the same hardware I just installed the good FC4 kernel on the rawhide box and rebooted with the hub+reader plugged in a boot time and repeated for the bad kernel. I'd have to look around more for something closer in sequence that works. dmesg.bad and dmesg.good to be attached in a moment. -jef Created attachment 124736 [details]
kernel-2.6.15-1.1948_FC5 boot dmesg with non-functional usb hub
Created attachment 124737 [details]
kernel-2.6.15-1.1831_FC4 dmesg with functional hub on boot
Created attachment 124738 [details]
kernel-2.6.15-1.1884_FC5 dmseg with non-functional hub at boot
Okay here is the oldest rawhide kernel that I can find locally on my systems.
kernel-2.6.15-1.1884_FC5 exhibits badness.
-jef
Perfect dmesgs. I already diffed them, saw that message about the configuration not selected. Unfortunately I'm a little under with other work. Yeah, I'm sure this isn't a particularly high priority issue. And well.. it gives me a plausible excuse to use with the household's financial officer to buy a usb-2 compliant hub. I wish i had a second rawhide box up and running of a different hardware vintage to cross compare. -jef It's may be ok physically, just descriptors are erroneous. Also, older kernels worked, so it's a regression, strictly speaking. I'll get to it, the question is only when. A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. my 4-port hub is working again. thank you kernel fairies! |