On 18.05.2018 16:04, Sudip Mukherjee wrote:
Hi Mathias,
On Fri, May 18, 2018 at 03:55:04PM +0300, Mathias Nyman wrote:
Hi,
Looks like event for Transfer block (TRB) at 0x32a21060 was never completed,
or at least not handled by xhci driver.
(either the event was never issued by hw, or something got messed up in the driver along the way)
HC doesn't look busted, it continues sending transfer completions events.
it is already at event 0x32a211d0, which is 23 TRBS later. (one TRB is 0x10)
This small log sinppet doesnt' say much about the reasons.
Can you enable tracing for xhci and send me the output.
I saw in another thread that you will ask for the trace log and so I
was making a kernel with tracer enabled. I was also thinking of getting
the logs from usbmon. Will that be of any help?
Not sure yet, in this case i think traces are most interesting, then dynamic debug messages
(which spams dmesg and affects timing) and last usbmon.
-Mathias
--
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
