Re: UAS problem
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 trace is: http://lockie.ca/1.mon.out Details from cat /sys/kernel/debug/usb/devices T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 2 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1 P: Vendor=1d6b ProdID=0003 Rev= 4.00 S: Manufacturer=Linux 4.0.5-1-ARCH xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:02:00.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0 D: Ver= 3.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs= 1 P: Vendor=0bc2 ProdID=2321 Rev= 1.00 S: Manufacturer=Seagate S: Product=Expansion S: SerialNumber=NA4CTS2P C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=144mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms I: If#= 0 Alt= 1 #EPs= 4 Cls=08(stor.) Sub=06 Prot=62 Driver=usb-storage E: Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms E: Ad=83(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms E: Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms -- 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
Re: UAS problem
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 That was easier than wireshark. 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 successfully. It's hard to say exactly what is causing all those errors. It could be a bad cable, or a bad connection, or a borderline component in the computer or the drive. It could even be caused by electromagnetic interference, such as a faulty fluorescent light fixture nearby. 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
Re: UAS problem
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 I think I did the trace correctly. The gzipped log is 350M though. http://lockie.ca/wireshark_usb.pcapng.gz 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 -- 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
Re: UAS problem
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 successfully. It's hard to say exactly what is causing all those errors. It could be a bad cable, or a bad connection, or a borderline component in the computer or the drive. It could even be caused by electromagnetic interference, such as a faulty fluorescent light fixture nearby. Alan Stern Did the -71 errors add up and eventually cause the unmount? -- 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
Re: UAS problem
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 Documentation/usb/usbmon.txt. Alan Stern That was easier than wireshark. 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 successfully. It's hard to say exactly what is causing all those errors. It could be a bad cable, or a bad connection, or a borderline component in the computer or the drive. It could even be caused by electromagnetic interference, such as a faulty fluorescent light fixture nearby. Alan Stern Maybe it was user error. :-( I had a USB3 extension cable from the computer to the USB3 female on the cable that goes to a micro-B on the drive. I connected the drive directly to the computer on a different port and it all seems to work. -- 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
Re: UAS problem
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 gzipped log is 350M though. http://lockie.ca/wireshark_usb.pcapng.gz -- 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
Re: UAS problem
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 device number 2 using xhci_hcd A lot of resets with no reason. You need to enable debugging for the storage driver. Regards Oliver -- 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
Re: UAS problem
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 xhci_hcd [ 234.357368] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd 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 -- 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
Re: UAS problem
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 driver. I use kernel-4.0.4 [58247.659416] usb-storage 3-1:1.0: USB Mass Storage device detected [58247.659614] scsi host7: usb-storage 3-1:1.0 [58248.662967] scsi 7:0:0:0: Direct-Access Seagate Expansion 0502 PQ: 0 ANSI: 6 It shows a fallback to the storage driver. That ought to happen. Your problem is caused by something else. You need to post more of your log. Especially the part around a drop. Regards Oliver -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majordomo@... More majordomo info at http://vger.kernel.org/majordomo-info.html [ 139.106143] usb 3-1: new SuperSpeed USB device number 2 using xhci_hcd [ 139.132116] usb 3-1: USB controller :02:00.0 does not support streams, which are required by the UAS driver. [ 139.132125] usb 3-1: Please try an other USB controller if you wish to use UAS. [ 139.132132] usb-storage 3-1:1.0: USB Mass Storage device detected [ 139.132729] scsi host7: usb-storage 3-1:1.0 [ 140.135776] scsi 7:0:0:0: Direct-Access Seagate Expansion 0502 PQ: 0 ANSI: 6 [ 140.140088] sd 7:0:0:0: [sde] Spinning up disk... [ 141.140166] ..ready [ 142.142958] sd 7:0:0:0: [sde] 1953525167 512-byte logical blocks: (1.00 TB/931 GiB) [ 142.294808] sd 7:0:0:0: [sde] Write Protect is off [ 142.294818] sd 7:0:0:0: [sde] Mode Sense: 4f 00 00 00 [ 142.295870] sd 7:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 142.306449] sde: sde1 [ 142.308711] sd 7:0:0:0: [sde] Attached SCSI disk [ 142.879370] EXT4-fs (sde1): warning: mounting fs with errors, running e2fsck is recommended [ 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 device number 2 using xhci_hcd [ 234.703794] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 235.319672] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 235.892637] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 236.532078] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 237.035027] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 237.451183] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 237.993835] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 238.819857] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 239.549080] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 240.008651] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 240.408239] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 240.741423] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 241.130174] xhci_hcd :02:00.0: HC gave bad length of 1024 bytes left [ 241.237440] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 241.373879] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 241.750196] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 242.066911] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 242.429794] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 249.050191] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 263.096483] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 263.715877] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 264.325368] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 265.081322] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 265.697476] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 265.877036] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 266.123441] xhci_hcd :02:00.0: HC gave bad length of 1024 bytes left [ 266.230195] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 266.686538] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 267.234008] xhci_hcd :02:00.0: HC gave bad length of 1024 bytes left [ 267.339130] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 267.791924] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 268.594685] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 269.250509] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 269.550236] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 269.869917] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 270.346196] usb 3-1: reset SuperSpeed USB device number 2 using xhci_hcd [
Re: UAS problem
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 [58247.659416] usb-storage 3-1:1.0: USB Mass Storage device detected [58247.659614] scsi host7: usb-storage 3-1:1.0 [58248.662967] scsi 7:0:0:0: Direct-Access Seagate Expansion 0502 PQ: 0 ANSI: 6 It shows a fallback to the storage driver. That ought to happen. Your problem is caused by something else. You need to post more of your log. Especially the part around a drop. Regards Oliver -- 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
UAS problem
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 [58247.659614] scsi host7: usb-storage 3-1:1.0 [58248.662967] scsi 7:0:0:0: Direct-Access Seagate Expansion 0502 PQ: 0 ANSI: 6 # lshw *-usb:3 description: USB controller product: SB7x0/SB8x0/SB9x0 USB EHCI Controller vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 13.2 bus info: pci@:00:13.2 version: 00 width: 32 bits clock: 66MHz capabilities: ehci bus_master cap_list configuration: driver=ehci-pci latency=32 resources: irq:17 memory:fe107000-fe1070ff -- 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
