* Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
@ 2021-11-12 9:37 DocMAX
2021-11-12 15:40 ` Alan Stern
0 siblings, 1 reply; 17+ messages in thread
From: DocMAX @ 2021-11-12 9:37 UTC (permalink / raw)
To: linux-usb
Hi there,
i would like to send a bug to you.
Issue in dmesg (lots of them):
sd 5:0:0:0: [sde] tag#4 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_OK cmd_age=19s
sd 5:0:0:0: [sde] tag#4 Sense Key : Illegal Request [current]
sd 5:0:0:0: [sde] tag#4 Add. Sense: Invalid command operation code
sd 5:0:0:0: [sde] tag#4 CDB: Write(16) 8a 00 00 00 00 00 85 33 72 e0 00
00 00 20 00 00
My workaround: kernel cmdline: usb-storage.quirks=2109:0715:u
My kernel: Linux zeus 5.14.16-arch1-1 #1 SMP PREEMPT Tue, 02 Nov 2021
22:22:59 +0000 x86_64 GNU/Linux
Would be cool if you can fix this.
Thanks,
Kr, DocMAX
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-12 9:37 Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor" DocMAX
@ 2021-11-12 15:40 ` Alan Stern
2021-11-12 16:04 ` DocMAX
0 siblings, 1 reply; 17+ messages in thread
From: Alan Stern @ 2021-11-12 15:40 UTC (permalink / raw)
To: DocMAX; +Cc: linux-usb
On Fri, Nov 12, 2021 at 10:37:59AM +0100, DocMAX wrote:
> Hi there,
>
> i would like to send a bug to you.
>
> Issue in dmesg (lots of them):
> sd 5:0:0:0: [sde] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK
> cmd_age=19s
> sd 5:0:0:0: [sde] tag#4 Sense Key : Illegal Request [current]
> sd 5:0:0:0: [sde] tag#4 Add. Sense: Invalid command operation code
> sd 5:0:0:0: [sde] tag#4 CDB: Write(16) 8a 00 00 00 00 00 85 33 72 e0 00 00
> 00 20 00 00
>
> My workaround: kernel cmdline: usb-storage.quirks=2109:0715:u
>
> My kernel: Linux zeus 5.14.16-arch1-1 #1 SMP PREEMPT Tue, 02 Nov 2021
> 22:22:59 +0000 x86_64 GNU/Linux
>
> Would be cool if you can fix this.
> Thanks,
Does this device have its own power source, or does it run off power
from the USB bus? This kind of error is fairly common when a drive
adapter doesn't have enough power.
Alan Stern
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-12 15:40 ` Alan Stern
@ 2021-11-12 16:04 ` DocMAX
2021-11-12 16:23 ` Alan Stern
0 siblings, 1 reply; 17+ messages in thread
From: DocMAX @ 2021-11-12 16:04 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb
It has it's own 60 watts power adapter. I doubt a usb-c port can power 4
x 3,5 inch hdd drives?
It's this enclosure by the way:
https://www.fantec.de/en/products/storage-devices/ssd-hard-drive-cases/35-inch-hard-drive-cases/produkt/details/artikel/1695_fantec_qb_35us3_6g-1/
Am 12.11.21 um 16:40 schrieb Alan Stern:
> Does this device have its own power source, or does it run off power
> from the USB bus? This kind of error is fairly common when a drive
> adapter doesn't have enough power.
>
> Alan Stern
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-12 16:04 ` DocMAX
@ 2021-11-12 16:23 ` Alan Stern
2021-11-12 16:26 ` DocMAX
0 siblings, 1 reply; 17+ messages in thread
From: Alan Stern @ 2021-11-12 16:23 UTC (permalink / raw)
To: DocMAX; +Cc: linux-usb
On Fri, Nov 12, 2021 at 05:04:54PM +0100, DocMAX wrote:
> It has it's own 60 watts power adapter. I doubt a usb-c port can power 4 x
> 3,5 inch hdd drives?
>
> It's this enclosure by the way:
> https://www.fantec.de/en/products/storage-devices/ssd-hard-drive-cases/35-inch-hard-drive-cases/produkt/details/artikel/1695_fantec_qb_35us3_6g-1/
Can you please provide the output from "lsusb -v" for this device?
Alan Stern
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-12 16:23 ` Alan Stern
@ 2021-11-12 16:26 ` DocMAX
2021-11-12 17:51 ` Alan Stern
0 siblings, 1 reply; 17+ messages in thread
From: DocMAX @ 2021-11-12 16:26 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb
Sure:
Bus 006 Device 006: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x2109 VIA Labs, Inc.
idProduct 0x0715 VL817 SATA Adaptor
bcdDevice 6.14
iManufacturer 1 VIA Labs,Inc.
iProduct 2 USB3.1 SATA Bridge
iSerial 3 0000000000000004
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0079
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 8mA
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 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)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 8
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 8
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
MaxStreams 8
Status pipe (0x02)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0046
bNumDeviceCaps 4
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
HIRD 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
Container ID Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 4
bReserved 0
ContainerID {510191c2-9ce8-c54e-bdcb-471b97c61daa}
SuperSpeedPlus USB Device Capability:
bLength 28
bDescriptorType 16
bDevCapabilityType 10
bmAttributes 0x00000023
Sublink Speed Attribute count 3
Sublink Speed ID count 1
wFunctionalitySupport 0x1100
bmSublinkSpeedAttr[0] 0x00050030
Speed Attribute ID: 0 5Gb/s Symmetric RX SuperSpeed
bmSublinkSpeedAttr[1] 0x000500b0
Speed Attribute ID: 0 5Gb/s Symmetric TX SuperSpeed
bmSublinkSpeedAttr[2] 0x000a4031
Speed Attribute ID: 1 10Gb/s Symmetric RX SuperSpeedPlus
bmSublinkSpeedAttr[3] 0x000a40b1
Speed Attribute ID: 1 10Gb/s Symmetric TX SuperSpeedPlus
Device Status: 0x0001
Self Powered
Bus 006 Device 005: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x2109 VIA Labs, Inc.
idProduct 0x0715 VL817 SATA Adaptor
bcdDevice 6.14
iManufacturer 1 VIA Labs,Inc.
iProduct 2 USB3.1 SATA Bridge
iSerial 3 0000000000000003
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0079
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 8mA
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 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)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 8
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 8
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
MaxStreams 8
Status pipe (0x02)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0046
bNumDeviceCaps 4
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
HIRD 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
Container ID Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 4
bReserved 0
ContainerID {bd40ee7c-d192-4a43-bf24-7cbf9090b1d5}
SuperSpeedPlus USB Device Capability:
bLength 28
bDescriptorType 16
bDevCapabilityType 10
bmAttributes 0x00000023
Sublink Speed Attribute count 3
Sublink Speed ID count 1
wFunctionalitySupport 0x1100
bmSublinkSpeedAttr[0] 0x00050030
Speed Attribute ID: 0 5Gb/s Symmetric RX SuperSpeed
bmSublinkSpeedAttr[1] 0x000500b0
Speed Attribute ID: 0 5Gb/s Symmetric TX SuperSpeed
bmSublinkSpeedAttr[2] 0x000a4031
Speed Attribute ID: 1 10Gb/s Symmetric RX SuperSpeedPlus
bmSublinkSpeedAttr[3] 0x000a40b1
Speed Attribute ID: 1 10Gb/s Symmetric TX SuperSpeedPlus
Device Status: 0x0001
Self Powered
Bus 006 Device 004: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x2109 VIA Labs, Inc.
idProduct 0x0715 VL817 SATA Adaptor
bcdDevice 6.14
iManufacturer 1 VIA Labs,Inc.
iProduct 2 USB3.1 SATA Bridge
iSerial 3 0000000000000002
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0079
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 8mA
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 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)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 8
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 8
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
MaxStreams 8
Status pipe (0x02)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0046
bNumDeviceCaps 4
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
HIRD 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
Container ID Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 4
bReserved 0
ContainerID {774a3fc1-ad31-a145-bdac-2fb12d791bd9}
SuperSpeedPlus USB Device Capability:
bLength 28
bDescriptorType 16
bDevCapabilityType 10
bmAttributes 0x00000023
Sublink Speed Attribute count 3
Sublink Speed ID count 1
wFunctionalitySupport 0x1100
bmSublinkSpeedAttr[0] 0x00050030
Speed Attribute ID: 0 5Gb/s Symmetric RX SuperSpeed
bmSublinkSpeedAttr[1] 0x000500b0
Speed Attribute ID: 0 5Gb/s Symmetric TX SuperSpeed
bmSublinkSpeedAttr[2] 0x000a4031
Speed Attribute ID: 1 10Gb/s Symmetric RX SuperSpeedPlus
bmSublinkSpeedAttr[3] 0x000a40b1
Speed Attribute ID: 1 10Gb/s Symmetric TX SuperSpeedPlus
Device Status: 0x0001
Self Powered
Bus 006 Device 003: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x2109 VIA Labs, Inc.
idProduct 0x0715 VL817 SATA Adaptor
bcdDevice 6.14
iManufacturer 1 VIA Labs,Inc.
iProduct 2 USB3.1 SATA Bridge
iSerial 3 0000000000000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0079
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 8mA
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 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)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 8
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 8
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
MaxStreams 8
Status pipe (0x02)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0046
bNumDeviceCaps 4
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
HIRD 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
Container ID Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 4
bReserved 0
ContainerID {cad2ca93-36b2-504d-8043-8e827bbe1b9b}
SuperSpeedPlus USB Device Capability:
bLength 28
bDescriptorType 16
bDevCapabilityType 10
bmAttributes 0x00000023
Sublink Speed Attribute count 3
Sublink Speed ID count 1
wFunctionalitySupport 0x1100
bmSublinkSpeedAttr[0] 0x00050030
Speed Attribute ID: 0 5Gb/s Symmetric RX SuperSpeed
bmSublinkSpeedAttr[1] 0x000500b0
Speed Attribute ID: 0 5Gb/s Symmetric TX SuperSpeed
bmSublinkSpeedAttr[2] 0x000a4031
Speed Attribute ID: 1 10Gb/s Symmetric RX SuperSpeedPlus
bmSublinkSpeedAttr[3] 0x000a40b1
Speed Attribute ID: 1 10Gb/s Symmetric TX SuperSpeedPlus
Device Status: 0x0001
Self Powered
Bus 006 Device 002: ID 2109:8822 VIA Labs, Inc. USB3.1 Hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.20
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 3
bMaxPacketSize0 9
idVendor 0x2109 VIA Labs, Inc.
idProduct 0x8822
bcdDevice 5.a3
iManufacturer 1 VIA Labs, Inc.
iProduct 2 USB3.1 Hub
iSerial 3 000000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x001f
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 19
Transfer Type Interrupt
Synch Type None
Usage Type Feedback
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 8
bMaxBurst 0
Hub Descriptor:
bLength 12
bDescriptorType 42
nNbrPorts 4
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
bPwrOn2PwrGood 175 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
bHubDecLat 0.4 micro seconds
wHubDelay 2292 nano seconds
DeviceRemovable 0x00
Hub Port Status:
Port 1: 0000.0203 lowspeed enable connect
Port 2: 0000.0203 lowspeed enable connect
Port 3: 0000.0203 lowspeed enable connect
Port 4: 0000.0203 lowspeed enable connect
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0049
bNumDeviceCaps 5
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000006
BESL 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 4 micro seconds
bU2DevExitLat 231 micro seconds
Container ID Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 4
bReserved 0
ContainerID {30eef35c-07d5-2549-b001-802d79434c30}
SuperSpeedPlus USB Device Capability:
bLength 28
bDescriptorType 16
bDevCapabilityType 10
bmAttributes 0x00000023
Sublink Speed Attribute count 3
Sublink Speed ID count 1
wFunctionalitySupport 0x1100
bmSublinkSpeedAttr[0] 0x00050030
Speed Attribute ID: 0 5Gb/s Symmetric RX SuperSpeed
bmSublinkSpeedAttr[1] 0x000500b0
Speed Attribute ID: 0 5Gb/s Symmetric TX SuperSpeed
bmSublinkSpeedAttr[2] 0x000a4031
Speed Attribute ID: 1 10Gb/s Symmetric RX SuperSpeedPlus
bmSublinkSpeedAttr[3] 0x000a40b1
Speed Attribute ID: 1 10Gb/s Symmetric TX SuperSpeedPlus
** UNRECOGNIZED: 03 10 0b
Device Status: 0x0001
Self Powered
Bus 005 Device 003: ID 2109:8818 VIA Labs, Inc. USB Billboard Device
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.01
bDeviceClass 17
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2109 VIA Labs, Inc.
idProduct 0x8818
bcdDevice 0.01
iManufacturer 1 VIA Labs, Inc.
iProduct 2 USB Billboard Device
iSerial 3 0000000000000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0012
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3 0000000000000001
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 17
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 3 0000000000000001
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0051
bNumDeviceCaps 3
Billboard Capability:
bLength 48
bDescriptorType 16
bDevCapabilityType 13
iAdditionalInfoURL 3 0000000000000001
bNumberOfAlternateModes 1
bPreferredAlternateMode 0
VCONN Power 0 1W
bmConfigured 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
bcdVersion 1.21
bAdditionalFailureInfo 0
bReserved 0
Alternate Modes supported by Device Container:
Alternate Mode 0 : Alternate Mode configuration successful
wSVID[0] 0xFF01
bAlternateMode[0] 0
iAlternateModeString[0] 3 0000000000000001
Billboard Alternate Mode Capability:
bLength 8
bDescriptorType 16
bDevCapabilityType 15
bIndex 0
dwAlternateModeVdo 0x05000000
Container ID Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 4
bReserved 0
ContainerID {30eef35c-07d5-2549-b001-802d79434c30}
Device Status: 0x0001
Self Powered
Bus 005 Device 002: ID 2109:2822 VIA Labs, Inc. USB2.0 Hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 2 TT per port
bMaxPacketSize0 64
idVendor 0x2109 VIA Labs, Inc.
idProduct 0x2822
bcdDevice 5.a3
iManufacturer 1 VIA Labs, Inc.
iProduct 2 USB2.0 Hub
iSerial 3 000000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0029
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 1 Single TT
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 2 TT per port
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 5
wHubCharacteristic 0x00e9
Per-port power switching
Per-port overcurrent protection
TT think time 32 FS bits
Port indicators
bPwrOn2PwrGood 175 * 2 milli seconds
bHubContrCurrent 100 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Port 3: 0000.0100 power
Port 4: 0000.0100 power
Port 5: 0000.0507 highspeed power suspend enable connect
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x0049
bNumDeviceCaps 5
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000006
BESL 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 4 micro seconds
bU2DevExitLat 231 micro seconds
Container ID Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 4
bReserved 0
ContainerID {30eef35c-07d5-2549-b001-802d79434c30}
SuperSpeedPlus USB Device Capability:
bLength 28
bDescriptorType 16
bDevCapabilityType 10
bmAttributes 0x00000023
Sublink Speed Attribute count 3
Sublink Speed ID count 1
wFunctionalitySupport 0x1100
bmSublinkSpeedAttr[0] 0x00050030
Speed Attribute ID: 0 5Gb/s Symmetric RX SuperSpeed
bmSublinkSpeedAttr[1] 0x000500b0
Speed Attribute ID: 0 5Gb/s Symmetric TX SuperSpeed
bmSublinkSpeedAttr[2] 0x000a4031
Speed Attribute ID: 1 10Gb/s Symmetric RX SuperSpeedPlus
bmSublinkSpeedAttr[3] 0x000a40b1
Speed Attribute ID: 1 10Gb/s Symmetric TX SuperSpeedPlus
** UNRECOGNIZED: 03 10 0b
Device Status: 0x0001
Self Powered
Am 12.11.21 um 17:23 schrieb Alan Stern:
> Can you please provide the output from "lsusb -v" for this device?
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-12 16:26 ` DocMAX
@ 2021-11-12 17:51 ` Alan Stern
2021-11-12 18:21 ` DocMAX
0 siblings, 1 reply; 17+ messages in thread
From: Alan Stern @ 2021-11-12 17:51 UTC (permalink / raw)
To: DocMAX; +Cc: linux-usb
On Fri, Nov 12, 2021 at 05:26:17PM +0100, DocMAX wrote:
> Sure:
>
> Bus 006 Device 006: ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 3.10
> bDeviceClass 0
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 9
> idVendor 0x2109 VIA Labs, Inc.
> idProduct 0x0715 VL817 SATA Adaptor
> bcdDevice 6.14
> iManufacturer 1 VIA Labs,Inc.
> iProduct 2 USB3.1 SATA Bridge
> iSerial 3 0000000000000004
Wow. Judging by the serial number values, you got the first four
devices of this sort ever made. (That is, unless they use the same
serial numbers on all of their devices!)
Anyway, the patch below should accomplish the same effect as the
module parameter override you've been using. Let us know if it works
properly.
Alan Stern
Index: usb-devel/drivers/usb/storage/unusual_devs.h
===================================================================
--- usb-devel.orig/drivers/usb/storage/unusual_devs.h
+++ usb-devel/drivers/usb/storage/unusual_devs.h
@@ -2291,6 +2291,13 @@ UNUSUAL_DEV( 0x2027, 0xa001, 0x0000, 0x
USB_SC_DEVICE, USB_PR_DEVICE, usb_stor_euscsi_init,
US_FL_SCM_MULT_TARG ),
+/* Reported by DocMAX <mail@vacharakis.de> */
+UNUSUAL_DEV( 0x2109, 0x0715, 0x0614, 0x0614,
+ "VIA Labs, Inc.",
+ "VL817 USB3.1 SATA Bridge",
+ USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+ US_FL_IGNORE_UAS),
+
UNUSUAL_DEV( 0x2116, 0x0320, 0x0001, 0x0001,
"ST",
"2A",
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-12 17:51 ` Alan Stern
@ 2021-11-12 18:21 ` DocMAX
2021-11-12 20:49 ` Alan Stern
0 siblings, 1 reply; 17+ messages in thread
From: DocMAX @ 2021-11-12 18:21 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb
The first and more buggy maybe.
So you are not going to fix this just blacklist uas by default?
I was so happy that i got a uas capable device and now the joy is
over... :-(
Is there detailed information of the uas/usb-storage differences? (Very
detailed, not just "it's faster")
On 12.11.21 18:51, Alan Stern wrote:
> Wow. Judging by the serial number values, you got the first four
> devices of this sort ever made. (That is, unless they use the same
> serial numbers on all of their devices!)
>
> Anyway, the patch below should accomplish the same effect as the
> module parameter override you've been using. Let us know if it works
> properly.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-12 18:21 ` DocMAX
@ 2021-11-12 20:49 ` Alan Stern
2021-11-12 20:57 ` DocMAX
0 siblings, 1 reply; 17+ messages in thread
From: Alan Stern @ 2021-11-12 20:49 UTC (permalink / raw)
To: DocMAX; +Cc: linux-usb
On Fri, Nov 12, 2021 at 07:21:34PM +0100, DocMAX wrote:
> The first and more buggy maybe.
> So you are not going to fix this just blacklist uas by default?
I don't understand what you mean. How could I fix a broken device?
If the device is unable to work with uas but _is_ able to work with
usb-storage, then disabling uas for it seems like the only possible way
to proceed.
> I was so happy that i got a uas capable device and now the joy is over...
> :-(
Do you know whether the device works with the UAS protocol under
Windows?
If you want more detailed information about exactly what is happening
in the communication between the computer and the device, you can
collect a usbmon trace. Or you can record the information going over
the bus using Wireshark (which I think will also work on Windows).
> Is there detailed information of the uas/usb-storage differences? (Very
> detailed, not just "it's faster")
I'm not aware of any such discussions, although ones probably exist
somewhere. The individual protocols are well described in documents
hosted on the usb.org web site, but as far as I know none of them talk
about the differences between the two protocols.
A quick summary of the major aspects would look like this:
The commands and status responses are bundled into packets in
slightly different ways (different packet headers and so on),
but this difference is relatively small.
uas uses USB streams, a feature of USB-3 not present in USB-2,
to issue multiple commands (and their associated data) in
parallel, allowing the device to process them in any order it
wants. usb-storage, by contrast, sends only one command at a
time and waits for it to complete before sending the next
command. That's the major difference between the protocols, and
it is what accounts for the difference in speed.
uas includes means for the computer to query the device about
the state of ongoing commands, which is not possible with
usb-storage.
Alan Stern
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-12 20:49 ` Alan Stern
@ 2021-11-12 20:57 ` DocMAX
2021-11-13 15:46 ` Alan Stern
0 siblings, 1 reply; 17+ messages in thread
From: DocMAX @ 2021-11-12 20:57 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb
So the problem is the device, not a driver issue? Wasn't aware of this.
Then do what has to be done. Thanks.
I read of lots of UAS issues with other hardware. Can someone recomment
a chipset which works rocket solid on linux with uas?
I don't want to do without UAS.
On 12.11.21 21:49, Alan Stern wrote:
> I don't understand what you mean. How could I fix a broken device?
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-12 20:57 ` DocMAX
@ 2021-11-13 15:46 ` Alan Stern
2021-11-13 20:51 ` DocMAX
0 siblings, 1 reply; 17+ messages in thread
From: Alan Stern @ 2021-11-13 15:46 UTC (permalink / raw)
To: DocMAX; +Cc: linux-usb
On Fri, Nov 12, 2021 at 09:57:47PM +0100, DocMAX wrote:
> So the problem is the device, not a driver issue? Wasn't aware of this. Then
> do what has to be done. Thanks.
Can you verify that the patch does fix the problem?
> I read of lots of UAS issues with other hardware. Can someone recomment a
> chipset which works rocket solid on linux with uas?
> I don't want to do without UAS.
I don't know of one, offhand, but there are plenty of them around. Lots
of people have drives using UAS that work just fine.
Alan Stern
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2021-11-13 15:46 ` Alan Stern
@ 2021-11-13 20:51 ` DocMAX
0 siblings, 0 replies; 17+ messages in thread
From: DocMAX @ 2021-11-13 20:51 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb
Sorry i'm not into coding very much. Can't do this task.
But i guess it will work if it does the same i did with the kernel
command line.
I don't know a single working UAS device for linux. (With 4 bays minimum).
On 13.11.21 16:46, Alan Stern wrote:
> Can you verify that the patch does fix the problem?
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
@ 2022-01-20 7:28 Thomas Weißschuh
2022-01-20 7:46 ` Greg KH
2022-01-20 14:42 ` Alan Stern
0 siblings, 2 replies; 17+ messages in thread
From: Thomas Weißschuh @ 2022-01-20 7:28 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb, DocMAX
Hi Alan,
I hava a IcyBox IB-3740-C31 [0], this device seems to be identical to the one
here. It has the same USB IDs and case design.
It also has the serial number "4".
The only difference it seems is the field bcdDevice which is "1.36" and the
reported name is different (see the patch below).
So I adapted the patch slightly to also match that bcdDevice.
I also changed the productName field but that does not seem to be used anyways.
Using the quirk flags "fgkm" as mentioned in [1] did not help.
FYI while there are many reports that UAS does not work with these devices,
there also are a few that report it working. For example [2].
diff --git a/drivers/usb/storage/unusual_devs.h b/drivers/usb/storage/unusual_devs.h
index 29191d33c0e3..53e8249644b2 100644
--- a/drivers/usb/storage/unusual_devs.h
+++ b/drivers/usb/storage/unusual_devs.h
@@ -2301,6 +2301,19 @@ UNUSUAL_DEV( 0x2027, 0xa001, 0x0000, 0x9999,
USB_SC_DEVICE, USB_PR_DEVICE, usb_stor_euscsi_init,
US_FL_SCM_MULT_TARG ),
+UNUSUAL_DEV( 0x2109, 0x0715, 0x0000, 0x9999,
+ "VIA Labs, Inc.",
+ "VL817 SATA Adaptor",
+ USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+ US_FL_IGNORE_UAS),
This is the exact issue:
[ 3606.231973] scsi host14: uas_eh_device_reset_handler start
[ 3606.232149] sd 14:0:0:0: [sdg] tag#2 uas_zap_pending 0 uas-tag 1 inflight: CMD
[ 3606.232154] sd 14:0:0:0: [sdg] tag#2 CDB: Write(16) 8a 00 00 00 00 00 18 0c c9 80 00 00 00 80 00 00
[ 3606.306257] usb 4-4.4: reset SuperSpeed Plus Gen 2x1 USB device number 11 using xhci_hcd
[ 3606.328584] scsi host14: uas_eh_device_reset_handler success
For this patch:
Tested-by: Thomas Weißschuh <linux@weissschuh.net>
Thomas
[0] https://icybox.de/en/product.php?id=155
[1] https://lore.kernel.org/linux-usb/c4b4aa34-12d9-7000-6398-d94a7ebffdfc@suse.com/
[2] https://spod.cx/blog/enabling_trim_support_via_VL817_usb_sata_adaptor.shtml
^ permalink raw reply related [flat|nested] 17+ messages in thread* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2022-01-20 7:28 Thomas Weißschuh
@ 2022-01-20 7:46 ` Greg KH
2022-01-20 14:42 ` Alan Stern
1 sibling, 0 replies; 17+ messages in thread
From: Greg KH @ 2022-01-20 7:46 UTC (permalink / raw)
To: Thomas Weißschuh; +Cc: Alan Stern, linux-usb, DocMAX
On Thu, Jan 20, 2022 at 08:28:30AM +0100, Thomas Weißschuh wrote:
> Hi Alan,
>
> I hava a IcyBox IB-3740-C31 [0], this device seems to be identical to the one
> here. It has the same USB IDs and case design.
> It also has the serial number "4".
> The only difference it seems is the field bcdDevice which is "1.36" and the
> reported name is different (see the patch below).
>
> So I adapted the patch slightly to also match that bcdDevice.
> I also changed the productName field but that does not seem to be used anyways.
>
> Using the quirk flags "fgkm" as mentioned in [1] did not help.
>
> FYI while there are many reports that UAS does not work with these devices,
> there also are a few that report it working. For example [2].
>
> diff --git a/drivers/usb/storage/unusual_devs.h b/drivers/usb/storage/unusual_devs.h
> index 29191d33c0e3..53e8249644b2 100644
> --- a/drivers/usb/storage/unusual_devs.h
> +++ b/drivers/usb/storage/unusual_devs.h
> @@ -2301,6 +2301,19 @@ UNUSUAL_DEV( 0x2027, 0xa001, 0x0000, 0x9999,
> USB_SC_DEVICE, USB_PR_DEVICE, usb_stor_euscsi_init,
> US_FL_SCM_MULT_TARG ),
>
> +UNUSUAL_DEV( 0x2109, 0x0715, 0x0000, 0x9999,
> + "VIA Labs, Inc.",
> + "VL817 SATA Adaptor",
> + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> + US_FL_IGNORE_UAS),
>
> This is the exact issue:
>
> [ 3606.231973] scsi host14: uas_eh_device_reset_handler start
> [ 3606.232149] sd 14:0:0:0: [sdg] tag#2 uas_zap_pending 0 uas-tag 1 inflight: CMD
> [ 3606.232154] sd 14:0:0:0: [sdg] tag#2 CDB: Write(16) 8a 00 00 00 00 00 18 0c c9 80 00 00 00 80 00 00
> [ 3606.306257] usb 4-4.4: reset SuperSpeed Plus Gen 2x1 USB device number 11 using xhci_hcd
> [ 3606.328584] scsi host14: uas_eh_device_reset_handler success
>
> For this patch:
>
> Tested-by: Thomas Weißschuh <linux@weissschuh.net>
>
> Thomas
>
> [0] https://icybox.de/en/product.php?id=155
> [1] https://lore.kernel.org/linux-usb/c4b4aa34-12d9-7000-6398-d94a7ebffdfc@suse.com/
> [2] https://spod.cx/blog/enabling_trim_support_via_VL817_usb_sata_adaptor.shtml
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- Your patch is malformed (tabs converted to spaces, linewrapped, etc.)
and can not be applied. Please read the file,
Documentation/email-clients.txt in order to fix this.
- Your patch does not have a Signed-off-by: line. Please read the
kernel file, Documentation/SubmittingPatches and resend it after
adding that line. Note, the line needs to be in the body of the
email, before the patch, not at the bottom of the patch or in the
email signature.
- You did not write a descriptive Subject: for the patch, allowing Greg,
and everyone else, to know what this patch is all about. Please read
the section entitled "The canonical patch format" in the kernel file,
Documentation/SubmittingPatches for what a proper Subject: line should
look like.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2022-01-20 7:28 Thomas Weißschuh
2022-01-20 7:46 ` Greg KH
@ 2022-01-20 14:42 ` Alan Stern
2022-01-20 17:39 ` Thomas Weißschuh
1 sibling, 1 reply; 17+ messages in thread
From: Alan Stern @ 2022-01-20 14:42 UTC (permalink / raw)
To: Thomas Weißschuh; +Cc: linux-usb, DocMAX
On Thu, Jan 20, 2022 at 08:28:30AM +0100, Thomas Weißschuh wrote:
> Hi Alan,
>
> I hava a IcyBox IB-3740-C31 [0], this device seems to be identical to the one
> here.
When you say "described here", do you mean "described earlier in this
email thread"? I ask because from the way you wrote that sentence, it
looks like you mean that the device described in [0] seems to be
identical to the one you have.
> It has the same USB IDs and case design.
> It also has the serial number "4".
> The only difference it seems is the field bcdDevice which is "1.36" and the
> reported name is different (see the patch below).
>
> So I adapted the patch slightly to also match that bcdDevice.
> I also changed the productName field but that does not seem to be used anyways.
>
> Using the quirk flags "fgkm" as mentioned in [1] did not help.
>
> FYI while there are many reports that UAS does not work with these devices,
> there also are a few that report it working. For example [2].
That's odd. And I don't really want to change the kernel in a way that
will cause those working devices to stop working with UAS.
> diff --git a/drivers/usb/storage/unusual_devs.h b/drivers/usb/storage/unusual_devs.h
> index 29191d33c0e3..53e8249644b2 100644
> --- a/drivers/usb/storage/unusual_devs.h
> +++ b/drivers/usb/storage/unusual_devs.h
> @@ -2301,6 +2301,19 @@ UNUSUAL_DEV( 0x2027, 0xa001, 0x0000, 0x9999,
> USB_SC_DEVICE, USB_PR_DEVICE, usb_stor_euscsi_init,
> US_FL_SCM_MULT_TARG ),
>
> +UNUSUAL_DEV( 0x2109, 0x0715, 0x0000, 0x9999,
> + "VIA Labs, Inc.",
> + "VL817 SATA Adaptor",
> + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> + US_FL_IGNORE_UAS),
Does the new patch fix your problem?
Alan Stern
> This is the exact issue:
>
> [ 3606.231973] scsi host14: uas_eh_device_reset_handler start
> [ 3606.232149] sd 14:0:0:0: [sdg] tag#2 uas_zap_pending 0 uas-tag 1 inflight: CMD
> [ 3606.232154] sd 14:0:0:0: [sdg] tag#2 CDB: Write(16) 8a 00 00 00 00 00 18 0c c9 80 00 00 00 80 00 00
> [ 3606.306257] usb 4-4.4: reset SuperSpeed Plus Gen 2x1 USB device number 11 using xhci_hcd
> [ 3606.328584] scsi host14: uas_eh_device_reset_handler success
>
> For this patch:
>
> Tested-by: Thomas Weißschuh <linux@weissschuh.net>
>
> Thomas
>
> [0] https://icybox.de/en/product.php?id=155
> [1] https://lore.kernel.org/linux-usb/c4b4aa34-12d9-7000-6398-d94a7ebffdfc@suse.com/
> [2] https://spod.cx/blog/enabling_trim_support_via_VL817_usb_sata_adaptor.shtml
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2022-01-20 14:42 ` Alan Stern
@ 2022-01-20 17:39 ` Thomas Weißschuh
2022-01-20 17:56 ` Alan Stern
0 siblings, 1 reply; 17+ messages in thread
From: Thomas Weißschuh @ 2022-01-20 17:39 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb, DocMAX
Hi Alan,
On 2022-01-20 09:42-0500, Alan Stern wrote:
> On Thu, Jan 20, 2022 at 08:28:30AM +0100, Thomas Weißschuh wrote:
> > Hi Alan,
> >
> > I hava a IcyBox IB-3740-C31 [0], this device seems to be identical to the one
> > here.
>
> When you say "described here", do you mean "described earlier in this
> email thread"? I ask because from the way you wrote that sentence, it
> looks like you mean that the device described in [0] seems to be
> identical to the one you have.
I meant the one described in this thread. I have the one sold at [0], which
looks identical except for the logo to the one described in the thread.
>
> > It has the same USB IDs and case design.
> > It also has the serial number "4".
> > The only difference it seems is the field bcdDevice which is "1.36" and the
> > reported name is different (see the patch below).
> >
> > So I adapted the patch slightly to also match that bcdDevice.
> > I also changed the productName field but that does not seem to be used anyways.
> >
> > Using the quirk flags "fgkm" as mentioned in [1] did not help.
> >
> > FYI while there are many reports that UAS does not work with these devices,
> > there also are a few that report it working. For example [2].
>
> That's odd. And I don't really want to change the kernel in a way that
> will cause those working devices to stop working with UAS.
This is why I brought it up. There are however many more reports online for
those devices where UAS does not work.
> > diff --git a/drivers/usb/storage/unusual_devs.h b/drivers/usb/storage/unusual_devs.h
> > index 29191d33c0e3..53e8249644b2 100644
> > --- a/drivers/usb/storage/unusual_devs.h
> > +++ b/drivers/usb/storage/unusual_devs.h
> > @@ -2301,6 +2301,19 @@ UNUSUAL_DEV( 0x2027, 0xa001, 0x0000, 0x9999,
> > USB_SC_DEVICE, USB_PR_DEVICE, usb_stor_euscsi_init,
> > US_FL_SCM_MULT_TARG ),
> >
> > +UNUSUAL_DEV( 0x2109, 0x0715, 0x0000, 0x9999,
> > + "VIA Labs, Inc.",
> > + "VL817 SATA Adaptor",
> > + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> > + US_FL_IGNORE_UAS),
>
> Does the new patch fix your problem?
Yes it does. As does disabling UAS via the usb-storage quirk parameter.
> Alan Stern
>
> > This is the exact issue:
> >
> > [ 3606.231973] scsi host14: uas_eh_device_reset_handler start
> > [ 3606.232149] sd 14:0:0:0: [sdg] tag#2 uas_zap_pending 0 uas-tag 1 inflight: CMD
> > [ 3606.232154] sd 14:0:0:0: [sdg] tag#2 CDB: Write(16) 8a 00 00 00 00 00 18 0c c9 80 00 00 00 80 00 00
> > [ 3606.306257] usb 4-4.4: reset SuperSpeed Plus Gen 2x1 USB device number 11 using xhci_hcd
> > [ 3606.328584] scsi host14: uas_eh_device_reset_handler success
> >
> > For this patch:
> >
> > Tested-by: Thomas Weißschuh <linux@weissschuh.net>
> >
> > Thomas
> >
> > [0] https://icybox.de/en/product.php?id=155
> > [1] https://lore.kernel.org/linux-usb/c4b4aa34-12d9-7000-6398-d94a7ebffdfc@suse.com/
> > [2] https://spod.cx/blog/enabling_trim_support_via_VL817_usb_sata_adaptor.shtml
Thomas
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2022-01-20 17:39 ` Thomas Weißschuh
@ 2022-01-20 17:56 ` Alan Stern
2022-01-21 20:39 ` Thomas Weißschuh
0 siblings, 1 reply; 17+ messages in thread
From: Alan Stern @ 2022-01-20 17:56 UTC (permalink / raw)
To: Thomas Weißschuh; +Cc: linux-usb, DocMAX
On Thu, Jan 20, 2022 at 06:39:51PM +0100, Thomas Weißschuh wrote:
> Hi Alan,
>
> On 2022-01-20 09:42-0500, Alan Stern wrote:
> > On Thu, Jan 20, 2022 at 08:28:30AM +0100, Thomas Weißschuh wrote:
> > > Hi Alan,
> > >
> > > I hava a IcyBox IB-3740-C31 [0], this device seems to be identical to the one
> > > here.
> >
> > When you say "described here", do you mean "described earlier in this
> > email thread"? I ask because from the way you wrote that sentence, it
> > looks like you mean that the device described in [0] seems to be
> > identical to the one you have.
>
> I meant the one described in this thread. I have the one sold at [0], which
> looks identical except for the logo to the one described in the thread.
> >
> > > It has the same USB IDs and case design.
> > > It also has the serial number "4".
> > > The only difference it seems is the field bcdDevice which is "1.36" and the
> > > reported name is different (see the patch below).
> > >
> > > So I adapted the patch slightly to also match that bcdDevice.
> > > I also changed the productName field but that does not seem to be used anyways.
> > >
> > > Using the quirk flags "fgkm" as mentioned in [1] did not help.
> > >
> > > FYI while there are many reports that UAS does not work with these devices,
> > > there also are a few that report it working. For example [2].
> >
> > That's odd. And I don't really want to change the kernel in a way that
> > will cause those working devices to stop working with UAS.
>
> This is why I brought it up. There are however many more reports online for
> those devices where UAS does not work.
It's a bad situation. It would be nice if we could figure out why some
of them work and others don't. Also, do these same devices work with UAS
in Windows or Mac OSX?
> > > diff --git a/drivers/usb/storage/unusual_devs.h b/drivers/usb/storage/unusual_devs.h
> > > index 29191d33c0e3..53e8249644b2 100644
> > > --- a/drivers/usb/storage/unusual_devs.h
> > > +++ b/drivers/usb/storage/unusual_devs.h
> > > @@ -2301,6 +2301,19 @@ UNUSUAL_DEV( 0x2027, 0xa001, 0x0000, 0x9999,
> > > USB_SC_DEVICE, USB_PR_DEVICE, usb_stor_euscsi_init,
> > > US_FL_SCM_MULT_TARG ),
> > >
> > > +UNUSUAL_DEV( 0x2109, 0x0715, 0x0000, 0x9999,
> > > + "VIA Labs, Inc.",
> > > + "VL817 SATA Adaptor",
> > > + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> > > + US_FL_IGNORE_UAS),
> >
> > Does the new patch fix your problem?
>
> Yes it does. As does disabling UAS via the usb-storage quirk parameter.
All right. I will submit the revised patch after the current merge
window is over.
Alan Stern
> > Alan Stern
> >
> > > This is the exact issue:
> > >
> > > [ 3606.231973] scsi host14: uas_eh_device_reset_handler start
> > > [ 3606.232149] sd 14:0:0:0: [sdg] tag#2 uas_zap_pending 0 uas-tag 1 inflight: CMD
> > > [ 3606.232154] sd 14:0:0:0: [sdg] tag#2 CDB: Write(16) 8a 00 00 00 00 00 18 0c c9 80 00 00 00 80 00 00
> > > [ 3606.306257] usb 4-4.4: reset SuperSpeed Plus Gen 2x1 USB device number 11 using xhci_hcd
> > > [ 3606.328584] scsi host14: uas_eh_device_reset_handler success
> > >
> > > For this patch:
> > >
> > > Tested-by: Thomas Weißschuh <linux@weissschuh.net>
> > >
> > > Thomas
> > >
> > > [0] https://icybox.de/en/product.php?id=155
> > > [1] https://lore.kernel.org/linux-usb/c4b4aa34-12d9-7000-6398-d94a7ebffdfc@suse.com/
> > > [2] https://spod.cx/blog/enabling_trim_support_via_VL817_usb_sata_adaptor.shtml
>
> Thomas
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor"
2022-01-20 17:56 ` Alan Stern
@ 2022-01-21 20:39 ` Thomas Weißschuh
0 siblings, 0 replies; 17+ messages in thread
From: Thomas Weißschuh @ 2022-01-21 20:39 UTC (permalink / raw)
To: Alan Stern; +Cc: linux-usb, DocMAX
On 2022-01-20 12:56-0500, Alan Stern wrote:
> On Thu, Jan 20, 2022 at 06:39:51PM +0100, Thomas Weißschuh wrote:
> > Hi Alan,
> >
> > On 2022-01-20 09:42-0500, Alan Stern wrote:
> > > On Thu, Jan 20, 2022 at 08:28:30AM +0100, Thomas Weißschuh wrote:
> > > > Hi Alan,
> > > >
> > > > I hava a IcyBox IB-3740-C31 [0], this device seems to be identical to the one
> > > > here.
> > >
> > > When you say "described here", do you mean "described earlier in this
> > > email thread"? I ask because from the way you wrote that sentence, it
> > > looks like you mean that the device described in [0] seems to be
> > > identical to the one you have.
> >
> > I meant the one described in this thread. I have the one sold at [0], which
> > looks identical except for the logo to the one described in the thread.
> > >
> > > > It has the same USB IDs and case design.
> > > > It also has the serial number "4".
> > > > The only difference it seems is the field bcdDevice which is "1.36" and the
> > > > reported name is different (see the patch below).
> > > >
> > > > So I adapted the patch slightly to also match that bcdDevice.
> > > > I also changed the productName field but that does not seem to be used anyways.
> > > >
> > > > Using the quirk flags "fgkm" as mentioned in [1] did not help.
> > > >
> > > > FYI while there are many reports that UAS does not work with these devices,
> > > > there also are a few that report it working. For example [2].
> > >
> > > That's odd. And I don't really want to change the kernel in a way that
> > > will cause those working devices to stop working with UAS.
> >
> > This is why I brought it up. There are however many more reports online for
> > those devices where UAS does not work.
>
> It's a bad situation. It would be nice if we could figure out why some
> of them work and others don't. Also, do these same devices work with UAS
> in Windows or Mac OSX?
The reports in both directions are all for Linux.
I don't have the setup to test it either, sorry.
> > > > diff --git a/drivers/usb/storage/unusual_devs.h b/drivers/usb/storage/unusual_devs.h
> > > > index 29191d33c0e3..53e8249644b2 100644
> > > > --- a/drivers/usb/storage/unusual_devs.h
> > > > +++ b/drivers/usb/storage/unusual_devs.h
> > > > @@ -2301,6 +2301,19 @@ UNUSUAL_DEV( 0x2027, 0xa001, 0x0000, 0x9999,
> > > > USB_SC_DEVICE, USB_PR_DEVICE, usb_stor_euscsi_init,
> > > > US_FL_SCM_MULT_TARG ),
> > > >
> > > > +UNUSUAL_DEV( 0x2109, 0x0715, 0x0000, 0x9999,
> > > > + "VIA Labs, Inc.",
> > > > + "VL817 SATA Adaptor",
> > > > + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> > > > + US_FL_IGNORE_UAS),
> > >
> > > Does the new patch fix your problem?
> >
> > Yes it does. As does disabling UAS via the usb-storage quirk parameter.
>
> All right. I will submit the revised patch after the current merge
> window is over.
Thanks!
> Alan Stern
>
> > > Alan Stern
> > >
> > > > This is the exact issue:
> > > >
> > > > [ 3606.231973] scsi host14: uas_eh_device_reset_handler start
> > > > [ 3606.232149] sd 14:0:0:0: [sdg] tag#2 uas_zap_pending 0 uas-tag 1 inflight: CMD
> > > > [ 3606.232154] sd 14:0:0:0: [sdg] tag#2 CDB: Write(16) 8a 00 00 00 00 00 18 0c c9 80 00 00 00 80 00 00
> > > > [ 3606.306257] usb 4-4.4: reset SuperSpeed Plus Gen 2x1 USB device number 11 using xhci_hcd
> > > > [ 3606.328584] scsi host14: uas_eh_device_reset_handler success
> > > >
> > > > For this patch:
> > > >
> > > > Tested-by: Thomas Weißschuh <linux@weissschuh.net>
> > > >
> > > > Thomas
> > > >
> > > > [0] https://icybox.de/en/product.php?id=155
> > > > [1] https://lore.kernel.org/linux-usb/c4b4aa34-12d9-7000-6398-d94a7ebffdfc@suse.com/
> > > > [2] https://spod.cx/blog/enabling_trim_support_via_VL817_usb_sata_adaptor.shtml
> >
> > Thomas
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2022-01-21 20:39 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-12 9:37 Issue with UAS and" VIA Labs, Inc. VL817 SATA Adaptor" DocMAX
2021-11-12 15:40 ` Alan Stern
2021-11-12 16:04 ` DocMAX
2021-11-12 16:23 ` Alan Stern
2021-11-12 16:26 ` DocMAX
2021-11-12 17:51 ` Alan Stern
2021-11-12 18:21 ` DocMAX
2021-11-12 20:49 ` Alan Stern
2021-11-12 20:57 ` DocMAX
2021-11-13 15:46 ` Alan Stern
2021-11-13 20:51 ` DocMAX
2022-01-20 7:28 Thomas Weißschuh
2022-01-20 7:46 ` Greg KH
2022-01-20 14:42 ` Alan Stern
2022-01-20 17:39 ` Thomas Weißschuh
2022-01-20 17:56 ` Alan Stern
2022-01-21 20:39 ` Thomas Weißschuh
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.