Via USB and ehci_hcd bug: USB not recognized - IRQ issue

[Cedric]

Binary package hint: linux-image-2.6-386

On Ubuntu Dapper Drake, with all updates applied, USB devices are not recognized anymore (they used to when Dapper was freshly released).

Problem may come from ehci_hcd, as removing this module (modprobe -r ehci_hcd) fix the issue, but then USB devices are stuck on 1.1 low speed standard.

Another solution seem to set acpi=noirq at boot time, but didn't fix the problem for me (it did for some other people however).

More googling showed me that this problem is ongoing and has appeared in the past as well. Some kernel issue here.

Here is what happens when I plug a USB device in (dmesg output):

[17185074.604000] usb 4-1: new high speed USB device using ehci_hcd and address 2
[17185075.604000] ehci_hcd 0000:00:10.3: Unlink after no-IRQ? Controller is probably using the wrong IRQ.
[17185086.148000] usb 4-1: device not accepting address 2, error -110
[17185086.260000] usb 4-1: new high speed USB device using ehci_hcd and address 3

"Controller is probably using the wrong IRQ" <- There we go: IRQ problem. Still, set acpi=noirq at boot time doesn't fix anything.

Here's my lspci output:

ced@chasiewbao:~$ lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:09.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference Card (rev 01)
0000:00:0a.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller (rev 20)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
0000:00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)

More information about this bug can be found on ubuntu forums at http://www.ubuntuforums.org/showthread.php?p=1220750

[Cedric (cedric-sydneyweb)]

This bug is not unconfirmed, thanks not to reject it. If you guys need more information (dmesg, lspci, etc.), simply ask. Querying for that bug on forums such as ubuntuforums.org will return a few threads, and even more if querying on other (non ubuntu) forums (google is your friend).

As mention, this bug has been introduced with a dapper kernel revision (initial dapper kernel was NOT affected).

I will be pleased to provide any information needed, but I do need help from kernel maintainers/developers to locate and fix the bug. Thanks.

Ced

P.S. here are 3 additional threads discussing a similar problem:

http://www.ubuntuforums.org/showthread.php?t=223647&highlight=ehci_hcd
http://www.ubuntuforums.org/showthread.php?t=226913&highlight=ehci_hcd
http://www.ubuntuforums.org/showthread.php?t=224851&highlight=ehci_hcd

[Hal Finkel (hal-finkel)]

I am also affected by this bug. I am running 2.6.15-26-686 on an Averatec 3250 laptop.

In addition to the threads listed above, the following thread has also appeared on the forums discussing this bug:
http://www.ubuntuforums.org/showthread.php?t=89266

for my system:
lspci:
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:09.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference Card (rev 01)
0000:00:0a.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
0000:00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)

The following are various filtered kernel logs from my system before connecting my USB harddrive, after connecting the USB harddrive, and then after removing the ehci driver.

dmesg | grep -i usb
[17179570.616000] SLPB PCI0 USB1 USB2 USB3 EHCI MC9 ILAN
[17179575.336000] usbcore: registered new driver usbfs
[17179575.336000] usbcore: registered new driver hub
[17179575.336000] USB Universal Host Controller Interface driver v2.3
[17179575.340000] uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
[17179575.340000] hub 1-0:1.0: USB hub found
[17179575.444000] uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
[17179575.444000] hub 2-0:1.0: USB hub found
[17179575.548000] uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
[17179575.548000] hub 3-0:1.0: USB hub found
[17179575.652000] ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
[17179575.652000] ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[17179575.652000] hub 4-0:1.0: USB hub found
[17186317.248000] usb 4-3: new high speed USB device using ehci_hcd and address 2
[17186328.792000] usb 4-3: device not accepting address 2, error -110
[17186333.124000] usb 4-3: new high speed USB device using ehci_hcd and address 4
[17186344.668000] usb 4-3: device not accepting address 4, error -110
[17186349.000000] usb 4-3: new high speed USB device using ehci_hcd and address 6
[17186360.544000] usb 4-3: device not accepting address 6, error -110
[17186364.876000] usb 4-3: new high speed USB device using ehci_hcd and address 8
[17186376.420000] usb 4-3: device not accepting address 8,...

[QuinnHarris (ubuntu-quinnh)]

Same problem same 2.6.15-26-686 on an Averatec 3250 laptop.

It worked fine on 2.6.15-25-686

Also check:
Bug 54273
Bug 24925

[Launchpad Janitor (janitor)]

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[penalvch (penalvch)]

Cedric, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one all the way at the bottom) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

n0PxN0p, please do not mark this a duplicate of another report, or vice versa, without a fully detailed technical discussion on the commit causing this problem.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]