On 01/08/2014 01:59 PM, David Laight wrote:
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
USB2.0 case was tested with ehci. Luckily my notebook has dedicated
USB2.0 port.
--
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
