USB failing

[Dean Henrichsmeyer]

After some idle time on my computer, I come back to no USB devices available. It happens irrespective of what's plugged into the computer. These errors show up in the kernel logs:

Feb 3 13:56:28 courage kernel: [24813.508940] usb 2-1.1: new high-speed USB device number 10 using ehci_hcd
Feb 3 13:56:28 courage kernel: [24813.599951] ehci_hcd 0000:00:1d.0: fatal error
Feb 3 13:56:28 courage kernel: [24813.603827] ehci_hcd 0000:00:1d.0: HC died; cleaning up
Feb 3 13:56:28 courage kernel: [24813.606553] ehci_hcd 0000:00:1d.0: force halt; handshake ffffc90000c68024 00004000 00004000 -> -110
Feb 3 13:56:28 courage kernel: [24813.606556] ehci_hcd 0000:00:1d.0: HC died; cleaning up
Feb 3 13:56:28 courage kernel: [24813.615806] usb 2-1.1: device descriptor read/all, error -108
Feb 3 13:56:28 courage kernel: [24813.615812] hub 2-1:1.0: cannot disable port 1 (err = -19)
Feb 3 13:56:28 courage kernel: [24813.615824] hub 2-1:1.0: cannot reset port 1 (err = -19)
Feb 3 13:56:28 courage kernel: [24813.615828] hub 2-1:1.0: cannot disable port 1 (err = -19)
Feb 3 13:56:28 courage kernel: [24813.615833] hub 2-1:1.0: cannot reset port 1 (err = -19)
Feb 3 13:56:28 courage kernel: [24813.615836] hub 2-1:1.0: cannot disable port 1 (err = -19)
Feb 3 13:56:28 courage kernel: [24813.615840] hub 2-1:1.0: cannot reset port 1 (err = -19)
Feb 3 13:56:28 courage kernel: [24813.615843] hub 2-1:1.0: cannot disable port 1 (err = -19)
Feb 3 13:56:28 courage kernel: [24813.615846] hub 2-1:1.0: unable to enumerate USB device on port 1
Feb 3 13:56:28 courage kernel: [24813.615849] hub 2-1:1.0: cannot disable port 1 (err = -19)
Feb 3 13:56:28 courage kernel: [24813.615855] usb 2-1.2: USB disconnect, device number 4
Feb 3 13:56:28 courage kernel: [24813.696177] usb 2-1.3: USB disconnect, device number 5
Feb 3 13:56:29 courage kernel: [24814.070611] usb 2-1.4: USB disconnect, device number 6
Feb 3 13:56:29 courage kernel: [24814.134540] usb 2-1.8: USB disconnect, device number 7
Feb 3 13:56:29 courage kernel: [24814.136242] usb 2-1: USB disconnect, device number 2

This did not happen at all with natty. Occasionally with oneiric, but it happens consistently all the time with precise.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image (not installed)
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dean 2327 F.... pulseaudio
 /dev/snd/controlC2: dean 2327 F.... pulseaudio
 /dev/snd/controlC0: dean 2327 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xfe700000 irq 46'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0887,102804aa,00100302 HDA:80862805,80862805,00100000'
   Controls : 49
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-0000:00:1d.0-1.2, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:0809'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 17
   Mono: Capture 8 [47%] [17.76dB] [on]
Card2.Amixer.info:
 Card hw:2 'Generic'/'HD-Audio Generic at 0xfe640000 irq 47'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 6
   Simple ctrls : 1
Card2.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Fri Feb 3 14:03:47 2012
HibernationDevice: RESUME=UUID=9d396be7-0dd3-4736-b372-dc350a0039b2
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Dell Inc. XPS 8300
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic root=UUID=d16fbb2d-b466-4e7e-a654-f170338c213f ro
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-12-generic N/A
 linux-backports-modules-3.2.0-12-generic N/A
 linux-firmware 1.68
RfKill:

SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0Y2MRG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/15/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: XPS 8300
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Dean Henrichsmeyer (dean)]

This happened again with the latest kernel...

Linux courage 3.2.0-14-generic #23-Ubuntu SMP Fri Feb 3 23:17:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

This is what was in the log..

[33389.823505] hub 2-1.1.1:1.0: cannot reset port 1 (err = -71)
[33389.858696] usb 2-1.1.1: USB disconnect, device number 8
[33389.858701] usb 2-1.1.1.1: USB disconnect, device number 9
[33389.870588] hub 2-1.1.1:1.0: cannot reset port 1 (err = -71)
[33389.870594] hub 2-1.1.1:1.0: cannot reset port 1 (err = -19)
[33389.870598] hub 2-1.1.1:1.0: cannot disable port 1 (err = -19)
[33389.870602] hub 2-1.1.1:1.0: cannot disable port 1 (err = -19)
[33389.871160] scsi 7:0:0:0: killing request
[33390.006453] hub 2-1.1:1.0: hub_port_status failed (err = -71)
[33390.006459] hub 2-1.1:1.0: connect-debounce failed, port 1 disabled
[33390.084515] usb 2-1.1: USB disconnect, device number 3
[88254.083802] hub 2-1:1.0: hub_port_status failed (err = -110)
[88257.829221] usb 2-1.1: new high-speed USB device number 10 using ehci_hcd
[88258.033156] ehci_hcd 0000:00:1d.0: fatal error
[88258.037018] ehci_hcd 0000:00:1d.0: HC died; cleaning up
[88258.037040] usb 2-1.1: device descriptor read/all, error -108
[88258.037048] hub 2-1:1.0: cannot disable port 1 (err = -19)
[88258.037071] hub 2-1:1.0: cannot reset port 1 (err = -19)
[88258.037077] hub 2-1:1.0: cannot disable port 1 (err = -19)
[88258.039747] ehci_hcd 0000:00:1d.0: force halt; handshake ffffc90000c68024 00004000 00004000 -> -110
[88258.039751] ehci_hcd 0000:00:1d.0: HC died; cleaning up
[88258.039762] hub 2-1:1.0: cannot reset port 1 (err = -19)
[88258.039766] hub 2-1:1.0: cannot disable port 1 (err = -19)
[88258.039771] hub 2-1:1.0: cannot reset port 1 (err = -19)
[88258.039776] hub 2-1:1.0: cannot disable port 1 (err = -19)
[88258.039781] hub 2-1:1.0: unable to enumerate USB device on port 1
[88258.039786] hub 2-1:1.0: cannot disable port 1 (err = -19)
[88258.039795] usb 2-1.2: USB disconnect, device number 4
[88258.140682] usb 2-1.3: USB disconnect, device number 5
[88258.463397] usb 2-1.4: USB disconnect, device number 6
[88258.591312] usb 2-1.8: USB disconnect, device number 7
[88258.597897] usb 2-1: USB disconnect, device number 2

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

Do you know if this issue happened in a previous kernel versions or releases, or is this a new issue?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc2 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc2'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc2-precise/

[Dean Henrichsmeyer (dean)]

I've been running 3.3.0-030300rc2-generic for a week and USB has not failed once.

[Dean Henrichsmeyer (dean)]

Just to be clear, this is a regression because the same computer worked flawlessly with Natty. This is stock Dell hardware.

[Joseph Salisbury (jsalisbury)]

Hi Dean,

Could you test one additional kernel? This is the latest upstream stable kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.7-precise/

This will tell us if the fix will find it's way into precise through the stable release update.

[Dean Henrichsmeyer (dean)]

I'm afraid I don't have good news. 3.2.7 crashed as well. Looks like it's a regression in 3.2.*.

For what it's worth - bug #912834 was automatically fixed when I upgraded to 3.3 as well so it seems that's also a 3.2.* regression.

[Joseph Salisbury (jsalisbury)]

Thanks for the update, Dean. I'll search upstream and see if the patch that fixes this issue in v3.3 will be queued up for 3.2 stable.

[Dean Henrichsmeyer (dean)]

Hold up on that just a bit. If I cold boot the machine, I can't get the latest precise kernel to crash (3.2.0-17-generic) and warm booting I was able to crash 3.3.*.

I don't know if the fact that a warm reboot causes it to crash indicates a hardware problem or a software problem, but whatever the problem, it appears present in all kernels. I don't mind cold booting for a stable system. :)

Let me run with 3.2.0-17 for a few more days to make sure that's indeed true and I'll comment on the ticket.

[Dean Henrichsmeyer (dean)]

OK, I can confirm that they all (3.3.0-rc5 through 3.2.7 to the current in precise 3.2.0-18) crash after a while. It seems to be a bug present everywhere :-(

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Dean Henrichsmeyer (dean)]

Somehow this was fixed in the kernel that shipped with precise.

[Lathan Bidwell (lathan)]

Pardon me if I'm reviving an old bug...

But I am experiencing this with 12.04 counter to what the last comment says.

I have a desktop at work, it only happens when I leave it idle (xscreensaver running) over the weekend.

I have a usb external harddrive, usb keyboard and mouse (mouse and keyboard through monitor usb hub).

When I come back on Monday morning, it never works, all USB ports are dead.

about 23 hours of inactivity I get this. And after it I start getting input/output errors on the usb hard drive (have a batch process running on it).

Aug 11 11:01:33 5700c-lathan kernel: [437078.190296] hub 2-1:1.0: cannot reset port 5 (err = -110)
Aug 11 11:01:34 5700c-lathan kernel: [437079.202267] hub 2-1:1.0: cannot reset port 5 (err = -110)
Aug 11 11:01:35 5700c-lathan kernel: [437080.214254] hub 2-1:1.0: cannot reset port 5 (err = -110)
Aug 11 11:01:36 5700c-lathan kernel: [437081.226196] hub 2-1:1.0: cannot reset port 5 (err = -110)
Aug 11 11:01:37 5700c-lathan kernel: [437082.238165] hub 2-1:1.0: cannot reset port 5 (err = -110)
Aug 11 11:01:37 5700c-lathan kernel: [437082.238168] hub 2-1:1.0: Cannot enable port 5. Maybe the USB cable is bad?
Aug 11 11:01:38 5700c-lathan kernel: [437083.250152] hub 2-1:1.0: cannot disable port 5 (err = -110)
Aug 11 11:01:39 5700c-lathan kernel: [437084.262127] hub 2-1:1.0: cannot disable port 5 (err = -110)
Aug 11 11:01:39 5700c-lathan kernel: [437084.262184] sd 7:0:0:0: Device offlined - not ready after error recovery
Aug 11 11:01:39 5700c-lathan kernel: [437084.262191] sd 7:0:0:0: [sdc] Unhandled error code
Aug 11 11:01:39 5700c-lathan kernel: [437084.262192] sd 7:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
Aug 11 11:01:39 5700c-lathan kernel: [437084.262194] sd 7:0:0:0: [sdc] CDB: Read(10): 28 00 6d b0 6e 97 00 00 10 00
Aug 11 11:01:39 5700c-lathan kernel: [437084.262199] end_request: I/O error, dev sdc, sector 1840279191
Aug 11 11:01:39 5700c-lathan kernel: [437084.262202] Buffer I/O error on device sdc1, logical block 230034891
Aug 11 11:01:39 5700c-lathan kernel: [437084.262204] Buffer I/O error on device sdc1, logical block 230034892
Aug 11 11:01:39 5700c-lathan kernel: [437084.262212] sd 7:0:0:0: rejecting I/O to offline device
Aug 11 11:01:39 5700c-lathan kernel: [437084.262214] sd 7:0:0:0: [sdc] killing request
Aug 11 11:01:39 5700c-lathan kernel: [437084.262222] sd 7:0:0:0: [sdc] Unhandled error code
Aug 11 11:01:39 5700c-lathan kernel: [437084.262223] sd 7:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Aug 11 11:01:39 5700c-lathan kernel: [437084.262224] sd 7:0:0:0: [sdc] CDB: Read(10): 28 00 52 9b 48 b7 00 00 28 00
Aug 11 11:01:39 5700c-lathan kernel: [437084.262228] end_request: I/O error, dev sdc, sector 1385908407
Aug 11 11:01:39 5700c-lathan kernel: [437084.262230] Buffer I/O error on device sdc1, logical block 173238543
Aug 11 11:01:39 5700c-lathan kernel: [437084.262233] Buffer I/O error on device sdc1, logical block 173238544
Aug 11 11:01:39 5700c-lathan kernel: [437084.262235] Buffer I/O error on device sdc1, logical block 173238545
Aug 11 11:01:39 5700c-lathan ntfs-3g[2483]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Aug 11 11:01:...

[Joseph Salisbury (jsalisbury)]

@lathan,

It would be best to open a new bug, so we can track it properly.

Thanks in advance!