> From: tatxarata
> Since reporting this bug I've invested some time to get myself familiar
> with USB protocol and analyzed attached capture files. It seems like
> device resetoccurs after device returns urb_status=-75 (-EOVERFLOW).
...
> In case of USB2.0 host<->device traffic looks pretty the same way as in
> case of USB3.0. Host also tries to read device by chunks of 240 sectors
> and device returns only 120. However for some reason this doesn't lead
> to EOVERFLOW.
Is that using ehci, or forcing xhci to run at USB2 speeds (eg by using
a USB2 extension cable)?
David
