On Tue, 12 Jan 2016, Ivan P wrote: > I've uploaded the usbmon traces here: > https://www.dropbox.com/sh/0gldb4r4g6p4p5w/AAAdmHP_Slya3f440v9oe1qka?dl=0 > > One run tracing every bus (0u), one run tracing only the sandisk stick (2u). > Each trace is from starting to copy the files to the point it hangs > up, at which I attempt to cd into the mount point. I looked at the second trace. It seems to indicate a bug in the xHCI host controller hardware or driver. Everything is okay almost up to the end. Here's where the trouble starts: > ffff8802fd7bf180 1135243584 S Bo:2:004:2 -115 31 = 55534243 1cc50200 00100000 80000a28 0000000d e0000008 00000000 000000 > ffff8802fd7bf180 1135243601 C Bo:2:004:2 0 31 > > ffff88028df546c0 1135243607 S Bi:2:004:1 -115 4096 < > ffff88028df546c0 1165404890 C Bi:2:004:1 -104 4096 = e83ad4f0 096d0965 b6e2cf54 9165f0e8 2a39d865 8e097d4d 2bef792c e0e7adaf This shows the computer trying to read 4 KB of data from the device. All of the data was received okay, but for some reason the transfer didn't end properly. Instead, it timed out after 30 seconds and was cancelled. That's the fundamental bug. Attempts to recover by resetting the device failed (apparently due to a bug in the device) and from that point on, nothing worked. The device kept reporting failures for each command, but with no error code. Since the original problem looks like an xHCI-related issue, maybe Mathias can suggest some things to try. Alan Stern -- 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
