Running openSUSE, kernel 4.7.2-1.g34ba8d6-default on a Dell Precision
M6500 and also on a recently built Core i7-5820K on an X99 chipset
Asrock mobo, I'm getting some odd but seemingly (so far) harmless
errors if I let the drive attach as a UAS device. Note that if I
force it into usbstorage mode everything works fine, so I don't think
it's a problem with the drive.
First, when I attach the drive, I get the following:
[ 174.486640] usb 3-2: new SuperSpeed USB device number 3 using xhci_hcd
[ 174.509024] usb 3-2: New USB device found, idVendor=0bc2, idProduct=ab28
[ 174.509029] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 174.509031] usb 3-2: Product: BUP BK
[ 174.509033] usb 3-2: Manufacturer: Seagate
[ 174.509035] usb 3-2: SerialNumber: NA7PJA0K
[ 174.512283] scsi host6: uas
[ 174.512880] scsi 6:0:0:0: Direct-Access Seagate BUP BK 0304
PQ: 0 ANSI: 6
[ 174.550681] sd 6:0:0:0: Attached scsi generic sg4 type 0
[ 174.551082] sd 6:0:0:0: [sdd] Spinning up disk...
[ 175.554433] .........ready
[ 183.587387] sd 6:0:0:0: [sdd] 7814037167 512-byte logical blocks: (4.00
TB/3.64 TiB)
[ 183.587393] sd 6:0:0:0: [sdd] 2048-byte physical blocks
[ 184.320881] sd 6:0:0:0: [sdd] Write Protect is off
[ 184.320889] sd 6:0:0:0: [sdd] Mode Sense: 4f 00 00 00
[ 184.321222] sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 184.387660] sd 6:0:0:0: [sdd] Attached SCSI disk
[ 197.922851] device-mapper: table: 254:0: adding target device sdd caused an
alignment inconsistency: physical_block_size=4096, logical_block_size=512,
alignment_offset=0, start=4096
[ 197.922857] device-mapper: table: 254:0: adding target device sdd caused an
alignment inconsistency: physical_block_size=4096, logical_block_size=512,
alignment_offset=0, start=4096
[ 198.248657] device-mapper: table: 254:0: adding target device sdd caused an
alignment inconsistency: physical_block_size=4096, logical_block_size=512,
alignment_offset=0, start=33553920
[ 198.248661] device-mapper: table: 254:0: adding target device sdd caused an
alignment inconsistency: physical_block_size=4096, logical_block_size=512,
alignment_offset=0, start=33553920
[ 199.809588] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts:
(null)
Then, when I write large volumes of data to the drive, I get the
following every few minutes or so, with the drive temporarily
stalling. The result is that on a drive capable of about 120 MB/sec I
actually get 40-60 MB/sec (it varies).
[ 475.006500] sd 6:0:0:0: [sdd] tag#15 uas_eh_abort_handler 0 uas-tag 16
inflight: CMD IN
[ 475.006509] sd 6:0:0:0: [sdd] tag#15 CDB: Read(16) 88 00 00 00 00 00 a3 81
00 4f 00 00 00 08 00 00
[ 475.006696] sd 6:0:0:0: [sdd] tag#7 uas_eh_abort_handler 0 uas-tag 8
inflight: CMD OUT
[ 475.006702] sd 6:0:0:0: [sdd] tag#7 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
ab ff 00 00 04 00 00 00
[ 475.006944] sd 6:0:0:0: [sdd] tag#6 uas_eh_abort_handler 0 uas-tag 7
inflight: CMD OUT
[ 475.006949] sd 6:0:0:0: [sdd] tag#6 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
a7 ff 00 00 04 00 00 00
[ 475.007266] sd 6:0:0:0: [sdd] tag#5 uas_eh_abort_handler 0 uas-tag 6
inflight: CMD OUT
[ 475.007272] sd 6:0:0:0: [sdd] tag#5 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
a3 ff 00 00 04 00 00 00
[ 475.007425] sd 6:0:0:0: [sdd] tag#4 uas_eh_abort_handler 0 uas-tag 5
inflight: CMD OUT
[ 475.007430] sd 6:0:0:0: [sdd] tag#4 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
9f ff 00 00 04 00 00 00
[ 475.007539] sd 6:0:0:0: [sdd] tag#3 uas_eh_abort_handler 0 uas-tag 4
inflight: CMD OUT
[ 475.007545] sd 6:0:0:0: [sdd] tag#3 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
9b ff 00 00 04 00 00 00
[ 475.007703] sd 6:0:0:0: [sdd] tag#2 uas_eh_abort_handler 0 uas-tag 3
inflight: CMD OUT
[ 475.007708] sd 6:0:0:0: [sdd] tag#2 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
97 ff 00 00 04 00 00 00
[ 475.007930] sd 6:0:0:0: [sdd] tag#14 uas_eh_abort_handler 0 uas-tag 15
inflight: CMD OUT
[ 475.007935] sd 6:0:0:0: [sdd] tag#14 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
93 ff 00 00 04 00 00 00
[ 475.008048] sd 6:0:0:0: [sdd] tag#1 uas_eh_abort_handler 0 uas-tag 2
inflight: CMD OUT
[ 475.008053] sd 6:0:0:0: [sdd] tag#1 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
8f ff 00 00 04 00 00 00
[ 475.008197] sd 6:0:0:0: [sdd] tag#0 uas_eh_abort_handler 0 uas-tag 1
inflight: CMD OUT
[ 475.008201] sd 6:0:0:0: [sdd] tag#0 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
8b ff 00 00 04 00 00 00
[ 475.008432] sd 6:0:0:0: [sdd] tag#13 uas_eh_abort_handler 0 uas-tag 14
inflight: CMD OUT
[ 475.008434] sd 6:0:0:0: [sdd] tag#13 CDB: Write(16) 8a 00 00 00 00 00 a3 8b
87 ff 00 00 04 00 00 00
[ 475.008514] scsi host6: uas_eh_bus_reset_handler start
[ 475.119728] usb 3-2: reset SuperSpeed USB device number 3 using xhci_hcd
[ 475.141103] scsi host6: uas_eh_bus_reset_handler success
The lsusb -v output for the drive:
Bus 003 Device 006: ID 0bc2:ab28 Seagate RSS LLC
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0bc2 Seagate RSS LLC
idProduct 0xab28
bcdDevice 1.00
iManufacturer 2 Seagate
iProduct 3 BUP BK
iSerial 1 NA7PJA0K
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 121
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 36mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
Command pipe (0x01)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x0000f41e
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
Device Status: 0x0000
(Bus Powered)
--
Robert Krawitz <[email protected]>
*** MIT Engineers A Proud Tradition http://mitathletics.com ***
Member of the League for Programming Freedom -- http://ProgFree.org
Project lead for Gutenprint -- http://gimp-print.sourceforge.net
"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
