Bug 110405
| Summary: | usb keyboard locks up randomly | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Aaron VanDevender <sig> | ||||||||
| Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 2 | CC: | evseenko | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | athlon | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2006-02-21 19:00:03 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
Aaron VanDevender
2003-11-19 04:47:59 UTC
Can the problem be reproduced this in text mode (Ctrl-Alt-F1)? Yes, problem can be reproduced in text mode. It gets reset by unplugging and plugging back in the keyboard, as it does in X. Problem persists in kernel 2.4.22-1.2129.nptl.athlon. Thanks heavens, text mode says we're in business. Please do this: get it to die, replug, if it resets ok and the box survives, run "dmesg > /tmp/dmesg.out" and attach dmesg.out to the bug (but do not drop into comments box). Created attachment 96364 [details]
output of dmesg after keyboard spaz and replug
Ok, I attached the output of dmesg.
Created attachment 97295 [details]
verbose usb kernel messages during freeze/replug
I recomplied the kernel to enable more verbose USB debugging output, then I
waited for the keyboard to freeze, and after replugging it, I saved the kernel
messages. Said messages have been attached.
Problem still exists with FC2 (kernel-2.6.5-1.358). I have demonstrated it now using two keyboards, and 2 motherboards. They keyboards are identical (Microsoft Natuarl Pro) but the mother boards are different. One is an Asus A7V600, and the other is an MSI KT6V-LSR. They are both based on the VIA KT600 chipset, and probably have the same USB controller. Both keyboards operate normally when plugged into a machine based on the KT400 chipset. Created attachment 101231 [details]
kernel log for keyboard error and replug
I built the newest kernel (2.6.6-1.435) using CONFIG_USB_DEBUG and added: #define DEBUG #define DEBUG_DATA to hid-core.c, hid-input.c, and usbkbd.c. It seems like every thing rolls along fine until the all the keyboard lights turn on and the keys go funny, and I get these kernel messages, until I replug: Jun 17 17:59:09 lazlo kernel: usb 2-1.1: control timeout on ep0in Jun 17 17:59:14 lazlo kernel: usb 2-1.1: control timeout on ep0in I've attached the whole kernel log in Comment #7. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ Even though this bug was marked FC1, it still exists in the latest FC2 kernels, and therefore doesn't deserve being closed with a WONTFIX and swept off to fedora legacy. However, if you insist, I can always open another bug that targets FC2 (and possibly FC3-test as well). Well, it's not as if David's script can read minds and know if a bug against FC1 can be applicable to FC2... :-) Aaron, I see you retargeted the bug already, so just reopen it then. Evidently this behavior is caused by having gpilotd running. It can't handle the poling of the USB that gpilotd does. There is some concensus that this is a hardware flaw rather than a software bug. Eitherway, its a dup. *** This bug has been marked as a duplicate of 128602 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |