On 06/09/15 10:13, Alan Stern wrote:
\Good grief, don't use wireshark! It captures every single byte of
data transferred, which is enormously more than what we need.
Instead, follow the instructions in Documentation/usb/usbmon.txt.
Alan Stern
That was easier than wireshark.
The usbmon
On Tue, 9 Jun 2015, James wrote:
On 06/09/15 10:13, Alan Stern wrote:
\Good grief, don't use wireshark! It captures every single byte of
data transferred, which is enormously more than what we need.
Instead, follow the instructions in Documentation/usb/usbmon.txt.
Alan Stern
On Tue, 9 Jun 2015, James wrote:
Alan Stern stern@... writes:
On Mon, 8 Jun 2015, Oliver Neukum wrote:
A lot of resets with no reason. You need to enable debugging
for the storage driver.
A usbmon trace would be easier to read and just as good for debugging.
Alan Stern
On 06/09/15 11:33, Alan Stern wrote:
The usbmon trace is:
http://lockie.ca/1.mon.out
The trace shows numerous -71 errors. These are low-level
communication errors, caused by noise in the USB cable or something of
that sort. In each case the system recovered and retried the failed
command
On 06/09/15 11:33, Alan Stern wrote:
On Tue, 9 Jun 2015, James wrote:
On 06/09/15 10:13, Alan Stern wrote:
\Good grief, don't use wireshark! It captures every single byte of
data transferred, which is enormously more than what we need.
Instead, follow the instructions in
Alan Stern stern@... writes:
On Mon, 8 Jun 2015, Oliver Neukum wrote:
A lot of resets with no reason. You need to enable debugging
for the storage driver.
A usbmon trace would be easier to read and just as good for debugging.
Alan Stern
I think I did the trace correctly.
The
On Sun, 2015-06-07 at 12:13 +, James wrote:
[ 142.892218] EXT4-fs (sde1): mounted filesystem with ordered data
mode.
Opts: (null)]
cp to drive
drop is next
[ 234.054404] usb 3-1: reset SuperSpeed USB device number 2 using
xhci_hcd
[ 234.357368] usb 3-1: reset SuperSpeed USB
On Mon, 8 Jun 2015, Oliver Neukum wrote:
On Sun, 2015-06-07 at 12:13 +, James wrote:
[ 142.892218] EXT4-fs (sde1): mounted filesystem with ordered data
mode.
Opts: (null)]
cp to drive
drop is next
[ 234.054404] usb 3-1: reset SuperSpeed USB device number 2 using
Oliver Neukum oneukum@... writes:
On Sun, 2015-06-07 at 04:19 +, James wrote:
I am having trouble with my USB3 drive, it drops the connection.
I found this in dmesg:
[59375.478410] usb 3-1: USB controller :02:00.0 does not support
streams, which are required by the UAS
On Sun, 2015-06-07 at 04:19 +, James wrote:
I am having trouble with my USB3 drive, it drops the connection.
I found this in dmesg:
[59375.478410] usb 3-1: USB controller :02:00.0 does not support
streams, which are required by the UAS driver.
I use kernel-4.0.4
I am having trouble with my USB3 drive, it drops the connection.
I found this in dmesg:
[59375.478410] usb 3-1: USB controller :02:00.0 does not support
streams, which are required by the UAS driver.
I use kernel-4.0.4
[58247.659416] usb-storage 3-1:1.0: USB Mass Storage device detected
11 matches
Mail list logo
