Hello, On 02/07/18 09:47, Oliver Neukum wrote: > obvious question, can you bisect it? It looks like a low level issue.
Yep. I had to skip a few commits towards the end of the bisection, because the compilation failed, but I ended up with: # only skipped commits left to test # possible first bad commit: [e6b20121c6d5d17d38ea93d1ec550713142e54c2] xhci: Add helper to get hardware dequeue pointer for stopped rings. # possible first bad commit: [8790736dbf2676ea398d8de952c791009290e3cc] xhci: Add stream id to xhci_dequeue_state structure # possible first bad commit: [cdd504e11391f0811a681d6efc680ca1e1c8ffac] xhci: Find out where an endpoint or stream stopped from its context. # possible first bad commit: [ed18c5fa945768a9bec994e786edbbbc7695acf6] usb: optimize acpi companion search for usb port devices # possible first bad commit: [11e1d25db643da9d620bfc53b14ff7151220b5fb] xhci: remove unused stopped_td pointer I checked out v4.14.18: it still had the bug. I then reverted these 5 commits, and could not witness the bug any more. > > [Tue Feb 6 22:18:28 2018] usb 4-2: reset SuperSpeed USB device number 10 > > using xhci_hcd > > Did you see this line with earlier kernels? On a machine running 4.11, I can see lines such as: "usb 1-2: new high-speed USB device number 10 using xhci_hcd" but nothing about "SuperSpeed" or "reset". Regards, Cyril. -- 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
