On Sat, 9 Sep 2017, Bruce Korb wrote: > Hi Alan, > > On Sat, Sep 9, 2017 at 12:48 PM, Alan Stern <st...@rowland.harvard.edu> wrote: > > Questions like this should always be sent to the linux-usb mailing > > list (CC'ed). > > I had the vein hope it was a known issue. > > > 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. > > Done (and copied to bug report also): > > # cat /sys/kernel/debug/usb/usbmon/2u ... > ffff880667cc5e00 1869399303 S Ii:2:007:1 -115:1 8 < > ffff880667cc5e00 1869466503 C Ii:2:007:1 -2:1 0 > ffff880667cc5e00 1869527243 S Ii:2:007:1 -115:1 8 < > ffff880667cc5e00 1869614516 C Ii:2:007:1 -2:1 0 > ffff880667cc5e00 1869631409 S Ii:2:007:1 -115:1 8 < > <<no response>>
It's a little surprising that the interrupt URB is cancelled twice and then restarted. But there's nothing wrong with that. I don't see anything else noteworthy in this. What do you obtain from usbmon when you plug the mouse directly into the computer? It's quite possible that your hub isn't working right. Have you tried testing with a different hub? Maybe a USB-2 hub rather than USB-3? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
