On Fri, 10 Apr 2015, Alistair Grant wrote: > I'm experiencing the revised bug reported in > https://bugzilla.kernel.org/show_bug.cgi?id=43541 It's hard to tell how much that bug report has in common with your problem, because no usbmon trace was ever provided for it. > i.e. the mouse works reliably in eHCI controllers, but not in xHCI > controllers (I've tried two different Intel xHCI controllers). The Have you tried testing a different mouse? > original bug report indicates that the problem is much harder to > reproduce with debugging switched on, however that hasn't been my > experience. While I have seen the mouse work with xHCI once or twice, I > haven't been able to get it working recently to capture a log. > > > Included below is the information requested at the time by Sarah Sharp, namely: > > * From the xHCI controller (plugging and unplugging the mouse) > ** usbmon log > ** /var/log/syslog with xhci_hcd module debugging enabled > ** sudo lspci -vvv > ** sudo lspci -vvv -n > * From the eHCI controller: > ** /var/log/syslog > ** sudo lsusb -v > > The xHCI testing is on kernel 4.0-rc7 (but also occurs on 3.19.3). > The eHCI information is from kernel 3.19.3. > > If you'd like any additional information, please let me know. Can you post the usbmon log for an EHCI controller? Comparing the two logs may be helpful. It appears that most, if not all, of the problem is caused by a bug in the mouse itself. You can see this in the lsusb output (even when the mouse was attached to an EHCI controller) ... > Bus 003 Device 005: ID 0458:003a KYE Systems Corp. (Mouse Systems) > NetScroll+ Mini Traveler / Genius NetScroll 120 > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0458 KYE Systems Corp. (Mouse Systems) > idProduct 0x003a NetScroll+ Mini Traveler / Genius NetScroll 120 > bcdDevice 0.00 > iManufacturer 1 Genius > iProduct 2 (error) ------------------------------^ ... here. The mouse should have provided a valid string for the Product name. In fact, your usbmon log shows that the mouse's firmware apparently crashed while the computer was attempting to retrieve the Product string, and that crash is what led to the -110 error. 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
