On Sat, 22 Mar 2014, Mike Mitchell wrote: > On Wed, Mar 19, 2014 at 12:51 PM, Alan Stern wrote: > > > > This trace doesn't show a 45-minute delay. It also doesn't show a > > > disconnect. Everything appears to be working normally. > > > > > The 3.5 kernel is getting old. Can you try something more recent, such > > > as 3.13? > > > > > Alan Stern > > > > I upgraded the kernel to : Linux enc006 3.13.6-031306-generic > #201403070154 SMP Okay, good. > I was optimistic that the device was detected at boot after the restart. > But then it disconnected again: > > Mar 21 21:28:44 enc006 kernel: [23321.382950] usb 2-1.1: USB disconnect, > device number 3 > Mar 21 21:28:44 enc006 kernel: [23321.631377] usb 2-1.1: new full-speed USB > device number 4 using ehci-pci > Mar 21 21:28:45 enc006 kernel: [23321.724156] usb 2-1.1: New USB device > found, idVendor=0d8c, idProduct=0008 > Mar 21 21:28:45 enc006 kernel: [23321.724164] usb 2-1.1: New USB device > strings: Mfr=0, Product=1, SerialNumber=0 > Mar 21 21:28:45 enc006 kernel: [23321.724169] usb 2-1.1: Product: C-Media > USB Audio Device > Mar 21 21:28:45 enc006 kernel: [23321.738614] input: C-Media USB Audio > Device as > /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input6 > Mar 21 21:28:45 enc006 kernel: [23321.738876] hid-generic > 0003:0D8C:0008.0002: input,hidraw0: USB HID v1.00 Device [C-Media USB Audio > Device ] on usb-0000:00:1d.0-1.1/input3 > Mar 22 00:20:22 enc006 kernel: [33618.155946] usb 2-1.1: USB disconnect, > device number 4 > > Then after the reboot, it was not detected right away again. Attached file > shows whole kern.log and delay in recognizing device after reboot. But > hese is the 42 minute part: > > Mar 22 10:52:40 enc006 kernel: [ 2564.269338] usb 2-1.1: new full-speed USB > device number 3 using ehci-pci > Mar 22 10:52:41 enc006 kernel: [ 2564.363243] usb 2-1.1: New USB device > found, idVendor=0d8c, idProduct=0008 > Mar 22 10:52:41 enc006 kernel: [ 2564.363252] usb 2-1.1: New USB device > strings: Mfr=0, Product=1, SerialNumber=0 > Mar 22 10:52:41 enc006 kernel: [ 2564.363256] usb 2-1.1: Product: C-Media > USB Audio Device > Mar 22 10:52:41 enc006 kernel: [ 2564.401169] hidraw: raw HID events driver > (C) Jiri Kosina > Mar 22 10:52:41 enc006 kernel: [ 2564.431416] usbcore: registered new > interface driver snd-usb-audio > Mar 22 10:52:41 enc006 kernel: [ 2564.431879] usbcore: registered new > interface driver usbhid > Mar 22 10:52:41 enc006 kernel: [ 2564.431884] usbhid: USB HID core driver > Mar 22 10:52:41 enc006 kernel: [ 2564.458741] input: C-Media USB Audio > Device as > /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input5 > Mar 22 10:52:41 enc006 kernel: [ 2564.459103] hid-generic > 0003:0D8C:0008.0001: input,hidraw0: USB HID v1.00 Device [C-Media USB Audio > Device ] on usb-0000:00:1d.0-1.1/input3 > > The 42 minute delay to recognition is remarkably consistent for this to be > a hardware problem. And I can;t help but think the disconnects are related. > I'm not sure if this is power, usbcore, or usbhid related. Where should I > be looking to get more detailed information? What happens if you run "lsusb -v" shortly after booting? Does that cause the mouse to be recognized? Anyway, here's something you can do: Collect a usbmon trace for bus 2. Detailed instructions are in the kernel source file Documentation/usb/usbmon.txt. Start the trace shortly after booting, while the mouse still hasn't been detected. Then while the trace is running, do the following: echo 0 >/sys/bus/usb/devices/2-1/bConfigurationValue and a few seconds later, echo 1 >/sys/bus/usb/devices/2-1/bConfigurationValue It's possible that this will cause the mouse to be detected, but if it doesn't, wait the 45 minutes (or however long it takes) before stopping the usbmon trace. Then post the output from the trace, and we'll see what it reveals. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
