Bug 666563
Summary: | Constant syslog errors: unable to enumerate USB device on port | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Roland Roberts <roland> | |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
Severity: | medium | Docs Contact: | ||
Priority: | low | |||
Version: | 15 | CC: | abeclaudius, adalbert.prokop, chrisa, gansalmon, itamar, jonathan, josdekloe, kernel-maint, kloe0040, madhu.chinakonda, renich, sha256sum | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 841738 (view as bug list) | Environment: | ||
Last Closed: | 2012-07-11 17:50:50 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
Roland Roberts
2010-12-31 21:16:02 UTC
Confirmed in F15 also. Also I see the same issue with F15. No devices plugged in, but a continuous stream of 'unable to enumerate' messages, both in the syslog (/var/log/messages) and also in the dmesg output. It causes the syslog file to grow fast (about a hundred new lines per minute) making it almost impossible to spot any other messages by eye without strict filtering. The dmesg output seems limited by about 1800 lines, so in just a few seconds all usefull information is gone from this output, making it really hard to (manually) get information on new usb devices plugged in etc. In addition: the message is also printed in all tty screens. Switching with control-alt-F2 just displays an endlessly repeating list of the same error with increasing timestamps. This makes it nearly impossible to fall back to the commandline in case you need to fix something with the graphical mode (i.e. manually kill a frozen application that uses full-screen etc.). You have to type blind and be really fast in spotting any commandline output you might need, or it is gone again. Seems to me a good enough reason to raise the urgency of this bug to medium or high. It seems these debian users are suffering from the same issue: http://lists.debian.org/debian-kernel/2011/04/msg00576.html they suspect it has to do with a recent nvidia hardware workaround. (I do have nvidia hardware in my laptop as well). So it seems not fedora specific. However, I don't seem to be running the ohci-hcd kernel module, so could not test what the effect of unloading it is (or is this compiled in the kernel on fedora systems? How to check this?) so I am not completely sure. I all, it is not only about Debian users, i´m using Fedora 15 and i got the same error. Upgrading from kernel 2.6.40-4.fc15 to kernel 2.6.40.3-0.fc15 (part of the default updates released past week by Fedora) seems to have solved this issue for me. At least I don't see other updates that I applied that day that can explain the fix. The full list of updates that I applied that day is: Aug 18 10:52:32 Updated: ibus-libs-1.3.99.20110419-14.fc15.x86_64 Aug 18 10:52:33 Updated: gnome-python2-extras-2.25.3-33.fc15.x86_64 Aug 18 10:52:34 Updated: ibus-gtk2-1.3.99.20110419-14.fc15.x86_64 Aug 18 10:53:00 Updated: ibus-1.3.99.20110419-14.fc15.x86_64 Aug 18 10:53:01 Updated: ibus-gtk3-1.3.99.20110419-14.fc15.x86_64 Aug 18 10:53:06 Updated: xulrunner-6.0-2.fc15.x86_64 Aug 18 10:53:07 Updated: httpd-tools-2.2.19-2.fc15.x86_64 Aug 18 10:53:13 Updated: httpd-2.2.19-2.fc15.x86_64 Aug 18 10:53:21 Updated: firefox-6.0-1.fc15.x86_64 Aug 18 10:53:22 Updated: gnome-python2-libegg-2.25.3-33.fc15.x86_64 Aug 18 10:53:22 Updated: gnome-python2-gtkhtml2-2.25.3-33.fc15.x86_64 Aug 18 10:53:23 Updated: gnome-python2-gtkspell-2.25.3-33.fc15.x86_64 Aug 18 10:54:02 Installed: kernel-devel-2.6.40.3-0.fc15.x86_64 Aug 18 10:54:07 Updated: yum-utils-1.1.31-2.fc15.noarch Aug 18 10:54:10 Updated: kernel-headers-2.6.40.3-0.fc15.x86_64 Aug 18 10:54:23 Installed: kernel-2.6.40.3-0.fc15.x86_64 I still have no idea what caused it or what fixed it, so if anyone has more information I would still be interested. This bug can however be closed I think. I still see the reported errors - many "unable to enumerate USB device" with kernel 2.6.40.3-0 (PAE and x86). I also have a NVidia video card (NForce2) Seems to be related to the kernel version. I've downgraded to 2.6.38.6 and the USB system works. I have this bug too in Fedora 16. Please update bug version number. I have this problem as well on Fedora 16, latest kernel (3.2.2.1.fc16_x86_64). It completely swamps messages.log There appears to be a fix for Debian as per this link: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635573 Perhaps this can be used to resolve the problem in Fedora. Right now I have only two choices: 1. Leave USB enabled in BIOS and have nothing but the "unable to enumerate USB device on port" messages in my messages logs (unending at the rate of about 3 or 4 a second) or 2. Disable USB in BIOS and be unable to use any attached USB devices. Still exists with latest kernel (Linux <machine name> 3.2.6-3.fc16.x86_64 #1 SMP Mon Feb 13 20:35:42 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux), with same terrible choices: no USB or basically useless messages.log As mentioned in comment 3, the fact that it swamps logs AND continues to exist across Fedora versions "Seems to me a good enough reason to raise the urgency of this bug to medium or high." Created a quick and dirty patch for drivers/usb/host/pci-quirks.c based on Debian fix mentioned in comment 11 at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635573 diff -uNrp kernel-3.2.fc16.orig/drivers/usb/host/pci-quirks.c kernel-3.2.fc16.new/drivers/usb/host/pci-quirks.c --- kernel-3.2.fc16.orig/drivers/usb/host/pci-quirks.c 2012-02-16 09:22:07.466625150 -0500 +++ kernel-3.2.fc16.new/drivers/usb/host/pci-quirks.c 2012-02-16 01:29:30.933895895 -0500 @@ -505,7 +505,7 @@ static void __devinit quirk_usb_handoff_ writel((u32) ~0, base + OHCI_INTRDISABLE); /* Reset the USB bus, if the controller isn't already in RESET */ - if (control & OHCI_HCFS) { + if ((control & OHCI_HCFS) || (pdev->vendor == PCI_VENDOR_ID_NVIDIA)) { /* Go into RESET, preserving RWC (and possibly IR) */ writel(control & OHCI_CTRL_MASK, base + OHCI_CONTROL); readl(base + OHCI_CONTROL); Tested on my box with NVIDIA proprietary kernel and VMWare Workstation, both of which are finicky - works perfectly. No more constant stream of "unable to enumerate USB device on port", USB (and everything else it seems) appears to be working. If there's anything else I can do to encourage/speed up fixing this bug, please let me know. BTW, the page on building your own kernel is FANTASTIC. http://fedoraproject.org/wiki/Building_a_custom_kernel One small niggle: I used a buildid of .USBPATCH001 which worked for creating the kernel, but was not recognized as newer than the release kernel version. Changing the buildid to .999 fixed that though. Debian bug report with fix http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635573 Most of this code seems to be in the latest kernel, except specifically targeting NVIDIA hardware to force drive bus reset for 50ms. Last entry for tonight, I promise :-) Problem still exists in latest Fedora 16 x86_64 kernel Linux mythpiggy 3.2.10-3.fc16.x86_64 #1 SMP Thu Mar 15 19:39:46 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Rebuild using patch above fixes the problem, until the next kernel update :( Fedora 15 has reached it's end of life as of June 26, 2012. As a result, we will not be fixing any remaining bugs found in Fedora 15. In the event that you have upgraded to a newer release and the bug you reported is still present, please reopen the bug and set the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. Thank you for taking the time to file a report. We hope newer versions of Fedora suit your needs. Please reopen and tag with F17. It is still a problem. |