On Mon, 8 Apr 2019, Bollinger, Seth wrote: > > On Apr 8, 2019, at 1:59 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx<mailto:stern@xxxxxxxxxxxxxxxxxxx>> wrote: > > > No, that trace did not show any failure. Did you see the corresponding > > error messages in the kernel log while you were collecting the trace? > > Maybe you can try again. > > I’m certain the last trace I sent should have contained the read. > > bulk A 000004bf ty 03 st 00000000 T 3584 L 0 ch 00000081 ep 1 fl 0 > BI completion: st 0 stat -75 AL 0 ec 0 returning -75 Hmmm. The usbmon trace doesn't contain a "-75" anywhere, and it should if the error above occurred while the trace was in progress. Is it possible that the problem occurs on the client rather than on the server? (You didn't say which machine produced the error messages in the log.) Perhaps simultaneous usbmon traces on both machines is the way to go. Alan Stern
