On Sat, 9 Sep 2017, Bruce Korb wrote: > Hi Alan, > > I've got another USB issue for you, this time it's software for sure > (as opposed to unqualified controller chips on the mobo) :). Questions like this should always be sent to the linux-usb mailing list (CC'ed). > I have filed a bug with the distro: > > https://bugzilla.suse.com/show_bug.cgi?id=1056960 > > but I'd rather get it fixed than wait for years. Anyway, is there any way > I can diagnose why the usbcore driver is not responding to mouse > interrupts on a particular bus? It was working fine before I upgraded > openSUSE, so there is some change that triggered the problem. > I went from 42.1 to 42.3, so it has been a couple of years since the > last time. > > T: Bus=02 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#= 5 Spd=12 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=046d ProdID=c245 Rev=69.00 > S: Manufacturer=Logitech > S: Product=Gaming Mouse G400 > C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=98mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid > I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid > > The mouse is seen and enumerated, but there is no response. > Should I whip up a debug flavor of usbcore, or is there a known issue? > > Thanks for any pointers! Regards, Bruce You should start by collecting another usbmon trace. This time: unplug the mouse, then start the trace, then plug the mouse into the hub and click it a few times, then stop the trace. That way we can see the exact sequence of everything that happens. 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
