When listening to my usb-bluetooth audio headset, the usb subsystem (I
think) on my laptop crashes, the bluetooth/audio is lost, and my
mplayer program is left in an "uninterruptible sleep" (D) state and
cannot be killed. The only way to get my usb-audio working again is to
reboot.
Interestingly, after the usb/audio crash occurs, when I plug in my usb
mouse to another port, it does get power, but isn't fully
detected/usable. My syslog shows many messages like:
kernel: hub 3-0:1.0: port 4 not reset yet, waiting 200ms
ohci-pci 0000:00:13.1: port[3] reset timeout, stat 00000311
hub 3-0:1.0: unable to enumerate USB device on port 4
And lastly:
kernel: hub 3-0:1.0: Cannot enable port 4. Maybe the USB cable is
bad?
In this state however, I am able to use my ehci-pci based usb-storage
thumbdrive.
However, after I disconnect the original usb audio device (that I
suspect somehow causes this problem), none of my usb devices (mouse,
thumbdrive, usb-bluetooth headset) work at all -- no power, no syslog
messages. The last message from syslog is from when I disconnect the
usb-audio device:
kernel: ohci-pci 0000:00:13.1: GetStatus roothub.portstatus [0]
= 0x00030100 PESC CSC PPS
kernel: hub 3-0:1.0: port 1, status 0100, change 0003, 12 Mb/s
kernel: usb 3-1: USB disconnect, device number 3
kernel: usb 3-1: unregistering device
kernel: usb 3-1: unregistering interface 3-1:1.0
The crash is difficult to reproduce, sometimes it can occur after a few
minutes of a clean boot, and sometimes after a few days. After the
audio/usb abruptly stops, the syslog simply says:
kernel: ALSA sound/usb/endpoint.c:501 timeout: still 3 active urbs on
EP #3
And then after a few minutes (after enabling some kernel debugging
options), I get some call traces of the hung task(s), which have
"ohci_urb_dequeue" in common.
http://dennisn.dyndns.org/guest/pubstuff/debug-usbaudio/crash1.log
http://dennisn.dyndns.org/guest/pubstuff/debug-usbaudio/crash2.log
http://dennisn.dyndns.org/guest/pubstuff/debug-usbaudio/crash3.log
The problem is not with my device, since it occurs with another
identical piece of hardware. It maybe be a problem with my laptop,
since my friend does not seem to be experiencing this problem, although
her laptop does not use ohci-pci.
My usb controllers are:
1002:4374 00:13.0 USB controller: Advanced Micro Devices [AMD]
nee ATI IXP SB400 USB Host Controller (prog-if 10 [OHCI])
1002:4375 00:13.1 USB controller: Advanced Micro Devices [AMD]
nee ATI IXP SB400 USB Host Controller (prog-if 10 [OHCI])
1002:4373 00:13.2 USB controller: Advanced Micro Devices [AMD]
nee ATI IXP SB400 USB2 Host Controller (prog-if 20 [EHCI])
The hardware device that seems to trigger the problem is the Logitech
one:
Bus 003 Device 002: ID 046d:0a29 Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
