You are not logged in.

#1 2012-04-24 10:16:43

lost eden
Member
Registered: 2008-01-01
Posts: 62

USB problems - hub_port_status failed (err = -110)

I'm running 64-bit Arch on a computer with an Asus P8P67 LE Rev 3.0 motherboard & have recently started to have serious USB issues. I've been doing some development with an Arduino microcontroller which has involved frequent connection/disconnection of USB devices & this seems to worsen the problem.

The machine will run fine, USB working perfectly, I can connect/disconnect devices & they work fine. But then I will connect some device (which I had used previously so I know not to be faulty) & I get something like the following;

Apr 23 13:06:23 localhost kernel: [ 4352.016561] usb 4-1.4: device descriptor read/64, error -32
Apr 23 13:06:23 localhost kernel: [ 4352.186402] usb 4-1.4: device descriptor read/64, error -32
Apr 23 13:06:24 localhost kernel: [ 4352.422942] usb 4-1.4: device descriptor read/64, error -32
Apr 23 13:07:56 localhost kernel: [ 4444.350916] usb 4-1.4: device descriptor read/64, error -32
Apr 23 13:07:56 localhost kernel: [ 4444.520744] usb 4-1.4: device descriptor read/64, error -32
Apr 23 13:07:56 localhost kernel: [ 4444.757146] usb 4-1.4: device descriptor read/64, error -32
Apr 23 14:11:57 localhost kernel: [ 8282.386352] usb 4-1.5: device descriptor read/all, error -110
Apr 23 14:11:58 localhost kernel: [ 8283.395388] hub 4-1:1.0: cannot disable port 5 (err = -110)
Apr 23 14:11:59 localhost kernel: [ 8284.404483] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:00 localhost kernel: [ 8285.413533] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:01 localhost kernel: [ 8286.422611] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:02 localhost kernel: [ 8287.431678] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:03 localhost kernel: [ 8288.440744] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:03 localhost kernel: [ 8288.440749] hub 4-1:1.0: Cannot enable port 5.  Maybe the USB cable is bad?
Apr 23 14:12:04 localhost kernel: [ 8289.449823] hub 4-1:1.0: cannot disable port 5 (err = -110)
Apr 23 14:12:05 localhost kernel: [ 8290.458889] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:06 localhost kernel: [ 8291.467949] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:07 localhost kernel: [ 8292.477034] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:08 localhost kernel: [ 8293.486109] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:09 localhost kernel: [ 8294.495178] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:09 localhost kernel: [ 8294.495183] hub 4-1:1.0: Cannot enable port 5.  Maybe the USB cable is bad?
Apr 23 14:12:10 localhost kernel: [ 8295.504267] hub 4-1:1.0: cannot disable port 5 (err = -110)
Apr 23 14:12:11 localhost kernel: [ 8296.513328] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:12 localhost kernel: [ 8297.522397] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:13 localhost kernel: [ 8298.531472] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:14 localhost kernel: [ 8299.540543] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:15 localhost kernel: [ 8300.549618] hub 4-1:1.0: cannot reset port 5 (err = -110)
Apr 23 14:12:15 localhost kernel: [ 8300.549623] hub 4-1:1.0: Cannot enable port 5.  Maybe the USB cable is bad?
Apr 23 14:12:16 localhost kernel: [ 8301.558688] hub 4-1:1.0: cannot disable port 5 (err = -110)
Apr 23 14:12:16 localhost kernel: [ 8301.558698] hub 4-1:1.0: unable to enumerate USB device on port 5
Apr 23 14:12:17 localhost kernel: [ 8302.567761] hub 4-1:1.0: cannot disable port 5 (err = -110)
Apr 23 14:12:22 localhost kernel: [ 8307.613128] hub 4-1:1.0: hub_port_status failed (err = -110)
Apr 23 14:12:46 localhost kernel: [ 8330.728529] hub 4-1:1.0: hub_port_status failed (err = -110)
Apr 23 14:12:51 localhost kernel: [ 8335.773950] hub 4-1:1.0: hub_port_status failed (err = -110)
Apr 23 14:12:56 localhost kernel: [ 8340.819236] hub 4-1:1.0: hub_port_status failed (err = -110)
Apr 23 14:13:01 localhost kernel: [ 8345.864605] hub 4-1:1.0: hub_port_status failed (err = -110)
Apr 23 14:13:06 localhost kernel: [ 8350.909955] hub 4-1:1.0: hub_port_status failed (err = -110)

Normally at this point any USB devices that were already connected to the computer (mouse, webcam) will continue to work fine, but any new device I connect isn't recognised at all (doesn't show in lsusb). The only way to correct the situation is to reboot the machine, which is far from convenient - I have been forced to reboot upwards of 5 times in a single day when trying to work with my Arduino.

In addition, the problem seemed to get another step worse yesterday. I had a few USB devices attached including a USB soundcard & was working away listening to music, when all of a sudden the music stopped & when I tailed the log the hub_port_status failed message was there again. So I hadn't connected or disconnected anything, it had sporadically broken!

I do not have a USB hub connected to the computer, the problem arises when using both the front & back USB ports. Incidentally I have exactly the same motherboard & processor in my computer at home (the computer with the problem is my computer at work) & have never had the issue, however I don't connect/disconnect USB devices to that one anywhere near as frequently.

So, any ideas? Is it a bug in software, or is the USB controller on this motherboard faulty?

Edit: the BIOS has an 'EHCI hand-off' feature that is currently disabled, will enabling it effect anything useful?

Last edited by lost eden (2012-04-24 10:42:02)

Offline

#2 2012-05-05 02:30:33

reverland
Member
Registered: 2012-03-25
Posts: 19

Re: USB problems - hub_port_status failed (err = -110)

I faced with the same problem on my arch64 on samsung r429 today.While some other ports may work

Offline

#3 2012-05-12 20:24:34

dennymallow
Member
Registered: 2011-07-08
Posts: 10

Re: USB problems - hub_port_status failed (err = -110)

Today I faced similar problems, so I think I'm not OT here... Here's my dmesg output:

May 12 21:53:19 merlinux kernel: [  860.673261] usb 5-1: device descriptor read/64, error -110
May 12 21:53:34 merlinux kernel: [  875.883268] usb 5-1: device descriptor read/64, error -110
May 12 21:53:50 merlinux kernel: [  891.199935] usb 5-1: device descriptor read/64, error -110
May 12 21:54:05 merlinux kernel: [  906.409933] usb 5-1: device descriptor read/64, error -110
May 12 21:54:10 merlinux kernel: [  911.637810] usb 5-1: device descriptor read/8, error -110
May 12 21:54:15 merlinux kernel: [  916.754812] usb 5-1: device descriptor read/8, error -110
May 12 21:54:21 merlinux kernel: [  921.981815] usb 5-1: device descriptor read/8, error -110
May 12 21:54:26 merlinux kernel: [  927.097816] usb 5-1: device descriptor read/8, error -110
May 12 21:54:26 merlinux kernel: [  927.199931] hub 5-0:1.0: unable to enumerate USB device on port 1

I realized after various attempts that logging into the system, opening a terminal and issuing a:

usb-devices

command, brings up again _all_ of the previously inactive usb devices.
My main problem was that the USB mouse got disabled with that "device descriptor" error -110 at startup, and it was annoying not to have a mouse after login.
To say all the truth, "usb-devices" stands still at a certain point of its execution for quite a long time: I guess that the problem lies just behind the moment in which usb-devices stucks!
But as I said, after about a 30s about pause it restores the faulty usb devices.
Really can't figure out (since I'm not so an advanced linux user) the reason for this behaviour!
I can only generically point my finger at the *huge* update I did this morning (was a little bit I didn't boot on my beloved Arch system, for many reasons...)

Just another note: before restoring the devices with usb-devices, lsusb does *not* show the inactive devices in the list. Maybe this is trivial for advanced users and its not so amazing, but I'm not so skilled so I felt I had to tell you also this little detail! smile


A good Arch can hold any weight!

Offline

#4 2012-05-12 22:16:09

dennymallow
Member
Registered: 2011-07-08
Posts: 10

Re: USB problems - hub_port_status failed (err = -110)

Nevermind...
My problem automagically went away by:

* turning off the PC
* unplugging the power cord
* plugging it back in (didn't wait too much to do this, few seconds)
* and finally booting up the system again

After this (apparently) silly "problem solving" action, I had no more hangs on udev events triggering during boot, and no more inactive USB devices at startup.
Everything was just... fine! yikes
I read about this odd solution on many threads all over the net.
Here's just one of those:
http://ubuntuforums.org/showthread.php? … st10054218

I'm a system programmer, and I know well that restarting stuff can be such a good solution, but... here we're going far beyond this concept! big_smile

Last edited by dennymallow (2012-05-12 22:24:09)


A good Arch can hold any weight!

Offline

Board footer

Powered by FluxBB