Bug 203278
| Summary: | keyboard and/or mouse randomly unrecognized via USB hub | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom Horsley <horsley1953> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | jonstanley, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | MassClosed | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-01-20 04:37:09 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: | |||
|
Description
Tom Horsley
2006-08-20 12:52:55 UTC
More data: Booted FC6t2 partition, and it did (once) recognize the mouse and keyboard via the hub. Decided to try some other stuff with the hub. Plugged in a littl thumb drive, nothing happened. lsusb shows: [root@zooty ~]# lsusb Bus 001 Device 001: ID 0000:0000 Bus 001 Device 002: ID 0aa8:8001 TriGem Computer, Inc. Bus 002 Device 001: ID 0000:0000 Bus 002 Device 002: ID 04cc:1521 Philips Semiconductors USB 2.0 Hub Bus 002 Device 003: ID 04a9:221c Canon, Inc. Bus 002 Device 005: ID 06a3:8000 Saitek PLC Bus 002 Device 006: ID 047d:1002 Kensington so the thumb drive doesn't show up at all. Leaving everything plugged into the hub, I unplug and plug the hub, now lsusb shows: Bus 001 Device 001: ID 0000:0000 Bus 001 Device 002: ID 0aa8:8001 TriGem Computer, Inc. Bus 002 Device 021: ID 05dc:a430 Lexar Media, Inc. Bus 002 Device 019: ID 047d:1002 Kensington Bus 002 Device 017: ID 06a3:8000 Saitek PLC Bus 002 Device 013: ID 04cc:1521 Philips Semiconductors USB 2.0 Hub Bus 002 Device 001: ID 0000:0000 Bus 002 Device 003: ID 04a9:221c Canon, Inc. So the thumb drive is there now (Lexar), but it wasn't mounted - opening the "my computer" in gnome doesn't show the lexar drive as it normally does when I plug it directly into the motherboard. I'll try booting FC6 a few more times to see if it suffers from the random failures like FC5. FC6 seems better with the mouse and keyboard. I've booted a few times now and it always recognized them, but the thumb drive is never recognized in the same hub (this smacks of someone special casing the keyboard and mouse somewhere to get them to work rather than fixing the general problem :-). However, I did have some kind of problem on FC6. I was tying in a gnome terminal and suddenly an infinite number of hyphen characters started spewing. Had to unplug the keyboard and plug into motherboard connector again to solve that one, so FC6, while better at initial recognition, still has problems when a hub is involved. Still never had a problem with initial recognition in FC6, but I also noticed some additional data points: The problem on FC6 is mainly that the keyboard will stop working after a while. I'm wondering if some kind of power management thing is interacting with usb - it turns everything off, then forget to turn it back on? The Windows box I tried this on has both usb 1.1 and usb 2.0 ports. It is definitely much flakier when I plug the hub into a 2.0 port. It takes much longer to "settle down" and fully recognize the mouse anhd keyboard following standby, and I can only bring it out of standby with the power switch, when I'm plugged into the usb 1.1 port, the keyboard will bring it out of standby. Despite the increased flakiness, everything does eventually work OK on the Windows box. Yet another box I tried is an old fedora core 4 system which has only usb 1.1 ports. On this box (still with the same hub) it is absolutely rock solid. Never once did I have a problem with recognition. It is beginning to look a lot like whatever is going on has something to do with usb 2.0 problems (unfortunately I have no usb 1.1 ports in my main machine, so I can't solve the problem by switching ports). My final data point for a while (I'm getting tired of experimenting :-). On FC6, if I find and turn off every power management option I can locate going through preferences and screen savers and wot not, the keyboard apparently works forever, seems as solid as the fedora core 4 box was. With all the default power management settings, if I leave it for a while and come back, the keyboard will be inoperative and I'll have to unplug it from the hub and plug it directly into the motherboard to get it back. Since my FC5 and FC6 testing is all on the same machine, it certainly seems to indicate that something is different at a software level and it isn't hardware (or not all hardware anyway) causing the problem. Well, I tried one more thing after all. I found another hub collecting dust because it had failed miserably the last time I tried to use it, but I gave it a whirl anyway, and in this case, it (so far) seems to be working perfectly. None of the symptoms have cropped up in either FC5 or FC6t2. This one shows up as: Bus 002 Device 002: ID 050d:0234 Belkin Components F5U234 USB 2.0 4-Port Hub instead of the Phillips one I'd been using before (sold as brand name "Targus"). I guess I'll stick with the Belkin for now (but the different behavior on FC5 and FC6t2 still makes it seem like some software is involved somewhere). This isn't a hal issue. Most likely a USB driver issue. Whereever the bug belongs, I can add that the Belkin hub has been working almost flawlessly since I added comment 5 above, but I have had it fail to recognize the mouse once after a reboot. Unpluging and pluging back in the mouse from the hub fixed that glitch. I did find that a usb->serial cable that I use for my cellphone doesn't work in the belkin hub (I think that was the original reason I concluded the hub was busted). If I plug it into the motherboard, it works fine. 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. (this is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug. |