On Sat, 22 Mar 2014, Dâniel Fraga wrote: > Extract with the mouse part: > > [ 4.428482] usb 2-1.6: new full-speed USB device number 7 using ehci-pci > [ 4.513395] usb 2-1.6: ep0 maxpacket = 8 > [ 4.516331] usb 2-1.6: skipped 1 descriptor after interface > [ 4.516702] usb 2-1.6: default language 0x0409 > [ 4.517954] usb 2-1.6: udev 7, busnum 2, minor = 134 > [ 4.517960] usb 2-1.6: New USB device found, idVendor=1532, idProduct=0016 > [ 4.517963] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > [ 4.517965] usb 2-1.6: Product: Razer DeathAdder > [ 4.517968] usb 2-1.6: Manufacturer: Razer > [ 4.518225] usb 2-1.6: usb_probe_device > [ 4.518228] usb 2-1.6: configuration #1 chosen from 1 choice > [ 4.518448] usb 2-1.6: adding 2-1.6:1.0 (config #1, interface 0) > [ 4.518613] usbhid 2-1.6:1.0: usb_probe_interface > [ 4.518615] usbhid 2-1.6:1.0: usb_probe_interface - got id > [ 6.118210] input: Razer Razer DeathAdder as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input9 > [ 26.738592] usb 2-1.6: ep 81: reserve intr @ 0+8 (0.0+1) [1/3 us] mask 1c01 > [ 26.738597] usb 2-1.6: link qh1-1c01/ffff8802153fb480 start 0 [1/3 us] > [ 26.759691] usb 2-1.6: unlink qh1-1c01/ffff8802153fb480 start 0 [1/3 us] > [ 27.546452] usb 2-1.6: link qh1-1c01/ffff8802153fb480 start 0 [1/3 us] That's more or less normal detection. I don't know why there was a 20-second gap, though. > [ 28.336116] usbhid 2-1.6:1.0: disconnect by usbfs > [ 28.336133] usb 2-1.6: unlink qh1-1c01/ffff8802153fb480 start 0 [1/3 us] > [ 28.353165] usb 2-1.6: manual set_interface for iface 0, alt 0 > [ 28.353168] usb 2-1.6: ep 81: release intr @ 0+8 (0.0+1) [1/3 us] mask 1c01 > [ 28.354041] usbhid 2-1.6:1.0: usb_probe_interface > [ 28.354044] usbhid 2-1.6:1.0: usb_probe_interface - got id > [ 28.356155] input: Razer Razer DeathAdder as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input10 > [ 28.356226] usb 2-1.6: ep 81: reserve intr @ 0+8 (0.0+1) [1/3 us] mask 1c01 > [ 28.356237] usb 2-1.6: link qh1-1c01/ffff8800d55d6300 start 0 [1/3 us] Is this the sort of thing you're seeing? The "disconnect by usbfs" means that some program on your computer is causing this to happen. The program unbinds the usbhid driver from the mouse and then rebinds it. If you want, I can post a patch that will print out the name of the process doing this. Did this happen when you were starting up KDE? > [ 28.356347] usbhid 2-1.6:1.0: disconnect by usbfs > [ 28.356358] usb 2-1.6: unlink qh1-1c01/ffff8800d55d6300 start 0 [1/3 us] > [ 28.381307] usb 2-1.6: manual set_interface for iface 0, alt 0 > [ 28.381311] usb 2-1.6: ep 81: release intr @ 0+8 (0.0+1) [1/3 us] mask 1c01 > [ 29.356447] usbhid 2-1.6:1.0: usb_probe_interface > [ 29.356452] usbhid 2-1.6:1.0: usb_probe_interface - got id > [ 29.358654] input: Razer Razer DeathAdder as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input11 > [ 29.358725] usb 2-1.6: ep 81: reserve intr @ 0+8 (0.0+1) [1/3 us] mask 1c01 > [ 29.358729] usb 2-1.6: link qh1-1c01/ffff8800d59ea900 start 0 [1/3 us] > [ 29.358999] usbhid 2-1.6:1.0: disconnect by usbfs > [ 29.359010] usb 2-1.6: unlink qh1-1c01/ffff8800d59ea900 start 0 [1/3 us] > [ 29.389647] usb 2-1.6: manual set_interface for iface 0, alt 0 > [ 29.389651] usb 2-1.6: ep 81: release intr @ 0+8 (0.0+1) [1/3 us] mask 1c01 > [ 30.358728] usbhid 2-1.6:1.0: usb_probe_interface > [ 30.358734] usbhid 2-1.6:1.0: usb_probe_interface - got id > [ 30.361130] input: Razer Razer DeathAdder as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input12 > [ 30.361228] usb 2-1.6: ep 81: reserve intr @ 0+8 (0.0+1) [1/3 us] mask 1c01 > [ 30.361232] usb 2-1.6: link qh1-1c01/ffff8802153c3600 start 0 [1/3 us] And then the same thing happened two more times. But at the end, the mouse was bound to the driver and so it should have been working properly. > 2) usbmon trace: > https://bugzilla.kernel.org/attachment.cgi?id=130331 I wasn't able to learn anything from the usbmon data. It just shows the mouse being used. Did one of those disconnection events occur while you were collecting the usbmon trace? > The device is the "2:007". I think you can grep it. I had to move the mouse a lot to trigger the bug. It > happens only when entering KDE and with intensive hard disk usage, high load. I could understand that maybe KDE is responsible for this sort of thing, but not intensive disk usage. That would not have any relation to usbfs. Can you post an equivalent dmesg log with the f1125f81feca commit reverted? 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
