On Tue, 11 Jun 2013, victor yeo wrote: > Yes, the matching gadget log and usbmon trace are attached in this > email. From the usbmon trace, the error (-108) is ESHUTDOWN from > SCSI_READ_10 command. From the gadget log, the last SCSI_READ_10 > command is received twice. First time it is ok, second time it causes > some problem. Which side could cause the ESHUTDOWN error?
The usbmon trace shows lots of errors. All those -75 (EOVERFLOW) status codes mean that the gadget sent a packet that was too large, i.e., more than 512 bytes. This happened in all the READ(10) commands except the last one -- none of them succeeded in transferring any data. After the last READ(10) command was sent, the usbmon trace shows that the host's USB port got disabled. Maybe because of the too-long packets. Whatever the reason, that's why the ESHUTDOWN error occurred. The gadget's log does indeed show that the last READ(10) was received twice. The second time is a bug in the UDC driver. No command was sent by the host, so the driver should not have reported that a command was received. 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
