Re: JMicron based usb 3.0 to sata enclosure, hangs, numerous errors
weird, not, it is little bit more stable, bu then it eventually hit the problem again: [ 2696.410684] sd 2:0:0:2: [sdc] tag#13 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD OUT [ 2696.410708] sd 2:0:0:2: [sdc] tag#13 CDB: Write(10) 2a 00 19 ed 69 80 00 00 20 00 [ 2696.410948] sd 2:0:0:2: [sdc] tag#12 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD OUT [ 2696.410967] sd 2:0:0:2: [sdc] tag#12 CDB: Write(10) 2a 00 19 ed 69 40 00 00 20 00 [ 2696.415259] sd 2:0:0:2: [sdc] tag#11 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD OUT [ 2696.415282] sd 2:0:0:2: [sdc] tag#11 CDB: Write(10) 2a 00 19 ed 69 00 00 00 20 00 [ 2696.418759] sd 2:0:0:2: [sdc] tag#10 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT [ 2696.418782] sd 2:0:0:2: [sdc] tag#10 CDB: Write(10) 2a 00 19 ed 68 20 00 00 60 00 [ 2696.422170] sd 2:0:0:2: [sdc] tag#9 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT [ 2696.422183] sd 2:0:0:2: [sdc] tag#9 CDB: Write(10) 2a 00 19 ed 67 80 00 00 40 00 [ 2696.425660] sd 2:0:0:2: [sdc] tag#8 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT [ 2696.425672] sd 2:0:0:2: [sdc] tag#8 CDB: Write(10) 2a 00 19 ed 66 e0 00 00 80 00 [ 2696.429160] sd 2:0:0:2: [sdc] tag#7 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT [ 2696.429171] sd 2:0:0:2: [sdc] tag#7 CDB: Write(10) 2a 00 19 ed 66 40 00 00 60 00 [ 2696.432661] sd 2:0:0:2: [sdc] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT [ 2696.432675] sd 2:0:0:2: [sdc] tag#6 CDB: Write(10) 2a 00 19 ed 5c 20 00 00 20 00 [ 2696.436263] sd 2:0:0:2: [sdc] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT [ 2696.436281] sd 2:0:0:2: [sdc] tag#5 CDB: Write(10) 2a 00 19 ed 5b a0 00 00 20 00 [ 2696.439746] sd 2:0:0:2: [sdc] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT [ 2696.439764] sd 2:0:0:2: [sdc] tag#4 CDB: Write(10) 2a 00 19 ed 5b 40 00 00 40 00 [ 2696.443236] sd 2:0:0:2: [sdc] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT [ 2696.443253] sd 2:0:0:2: [sdc] tag#3 CDB: Write(10) 2a 00 19 ed 59 e0 00 00 20 00 [ 2696.446657] sd 2:0:0:2: [sdc] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT [ 2696.44] sd 2:0:0:2: [sdc] tag#2 CDB: Write(10) 2a 00 19 ed 59 00 00 00 20 00 [ 2696.450164] sd 2:0:0:2: [sdc] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT [ 2696.450172] sd 2:0:0:2: [sdc] tag#1 CDB: Write(10) 2a 00 19 ed 58 80 00 00 60 00 [ 2696.453703] sd 2:0:0:1: [sdb] tag#26 uas_eh_abort_handler 0 uas-tag 27 inflight: CMD OUT [ 2696.453712] sd 2:0:0:1: [sdb] tag#26 CDB: Write(10) 2a 00 00 4d a9 80 00 00 20 00 [ 2696.457284] sd 2:0:0:1: [sdb] tag#25 uas_eh_abort_handler 0 uas-tag 26 inflight: CMD OUT [ 2696.457293] sd 2:0:0:1: [sdb] tag#25 CDB: Write(10) 2a 00 00 4d a9 40 00 00 20 00 [ 2696.461226] sd 2:0:0:1: [sdb] tag#24 uas_eh_abort_handler 0 uas-tag 25 inflight: CMD OUT [ 2696.461249] sd 2:0:0:1: [sdb] tag#24 CDB: Write(10) 2a 00 00 4d a9 00 00 00 20 00 [ 2696.464934] sd 2:0:0:1: [sdb] tag#23 uas_eh_abort_handler 0 uas-tag 24 inflight: CMD OUT [ 2696.464958] sd 2:0:0:1: [sdb] tag#23 CDB: Write(10) 2a 00 00 4d a8 20 00 00 60 00 [ 2696.468555] sd 2:0:0:1: [sdb] tag#22 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD OUT [ 2696.468569] sd 2:0:0:1: [sdb] tag#22 CDB: Write(10) 2a 00 00 4d a7 80 00 00 40 00 [ 2696.471942] sd 2:0:0:1: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 22 inflight: CMD OUT [ 2696.471955] sd 2:0:0:1: [sdb] tag#0 CDB: Write(10) 2a 00 00 4d a6 e0 00 00 80 00 [ 2696.475759] sd 2:0:0:1: [sdb] tag#21 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT [ 2696.475773] sd 2:0:0:1: [sdb] tag#21 CDB: Write(10) 2a 00 00 4d a6 40 00 00 60 00 [ 2696.479231] sd 2:0:0:1: [sdb] tag#20 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD OUT [ 2696.479248] sd 2:0:0:1: [sdb] tag#20 CDB: Write(10) 2a 00 00 4d 9c 20 00 00 20 00 [ 2696.482706] sd 2:0:0:1: [sdb] tag#19 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD OUT [ 2696.482722] sd 2:0:0:1: [sdb] tag#19 CDB: Write(10) 2a 00 00 4d 9b a0 00 00 20 00 [ 2696.486396] sd 2:0:0:1: [sdb] tag#18 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD OUT [ 2696.486410] sd 2:0:0:1: [sdb] tag#18 CDB: Write(10) 2a 00 00 4d 9b 40 00 00 40 00 [ 2696.490218] sd 2:0:0:1: [sdb] tag#17 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD OUT [ 2696.490236] sd 2:0:0:1: [sdb] tag#17 CDB: Write(10) 2a 00 00 4d 99 e0 00 00 20 00 [ 2696.494186] sd 2:0:0:1: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD OUT [ 2696.494215] sd 2:0:0:1: [sdb] tag#16 CDB: Write(10) 2a 00 00 4d 99 00 00 00 20 00 [ 2696.498156] sd 2:0:0:1: [sdb] tag#15 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD OUT [ 2696.498178] sd 2:0:0:1: [sdb] tag#15 CDB: Write(10) 2a 00 00 4d 98 80 00 00 60 00 [ 2696.501622] sd 2:0:0:1: [sdb] tag#14 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD OUT [ 2696.501630] sd 2:0:0:1: [sdb] tag#14 CDB: Write(10) 2a 00 00 4d 97 00 00 00 20 00 [ 2696.505850] scsi host2: uas_eh_device_reset_handler start [ 2696.587283] usb 2-1.4: reset SuperSpeed USB device number 4 using xhci_hcd [ 2696.611371] scsi ho
Re: JMicron based usb 3.0 to sata enclosure, hangs, numerous errors
Upgraded to 4.15.3 and now UAS works, strange... Anyhow now the enclosure is connected via an USB 3.0 HUB (self powered in my case) and it seems to be stable Devs, apparently there is some problem operating this chipset with Intel USB controller directly I have googled a little bit aroud and actually found someone complaining of a possible similar issue also on Windows: http://goughlui.com/2015/11/01/review-orico-usb-3-0-5-bay-raid-hdd-enclosure-9558ru3-part-2/ Note that the USB controller I have is identical to the Chris one: 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:22b5] (rev 36) (prog-if 30 [XHCI]) Subsystem: Intel Corporation Device [8086:7270] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 2018-02-14 8:36 GMT+01:00 Menion : > That is very strange > My device has same vid:pid of your one, but it goes blacklisted... > I am running kernel 4.15.1, I will try to upgrade > What kind of enclosure is yours? Mine is an Orico 9553RU3 5 bay > enclosure with RAID > Bye > > 2018-02-13 23:41 GMT+01:00 Chris Murphy : >> On Mon, Feb 12, 2018 at 12:57 AM, Menion wrote: >> >>> >>> I wanted to test my enclosure with an hub, but I have just realized >>> that now the JMS567 is UAS blacklisted by default in kernel >>> 4.15.x. >>> Can you check if it still works removing the dedicated hub external >>> power supply? >> >> >> I've upgraded to 4.15.3, and it does not appear to be blacklisted for uas >> driver. >> >> kernel: usbcore: registered new interface driver usb-storage >> kernel: scsi host2: uas >> kernel: usbcore: registered new interface driver uas >> >> >> >> Full kernel messages upon insertion directly to the computer's USB port >> (hub not involved at all): >> https://paste.fedoraproject.org/paste/bPPAl~ngYjktfC--i7NqJA/raw >> >> >> >> -- >> Chris Murphy -- 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: JMicron based usb 3.0 to sata enclosure, hangs, numerous errors
That is very strange My device has same vid:pid of your one, but it goes blacklisted... I am running kernel 4.15.1, I will try to upgrade What kind of enclosure is yours? Mine is an Orico 9553RU3 5 bay enclosure with RAID Bye 2018-02-13 23:41 GMT+01:00 Chris Murphy : > On Mon, Feb 12, 2018 at 12:57 AM, Menion wrote: > >> >> I wanted to test my enclosure with an hub, but I have just realized >> that now the JMS567 is UAS blacklisted by default in kernel >> 4.15.x. >> Can you check if it still works removing the dedicated hub external >> power supply? > > > I've upgraded to 4.15.3, and it does not appear to be blacklisted for uas > driver. > > kernel: usbcore: registered new interface driver usb-storage > kernel: scsi host2: uas > kernel: usbcore: registered new interface driver uas > > > > Full kernel messages upon insertion directly to the computer's USB port > (hub not involved at all): > https://paste.fedoraproject.org/paste/bPPAl~ngYjktfC--i7NqJA/raw > > > > -- > Chris Murphy -- 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: JMicron based usb 3.0 to sata enclosure, hangs, numerous errors
On Mon, Feb 12, 2018 at 12:57 AM, Menion wrote: > > I wanted to test my enclosure with an hub, but I have just realized > that now the JMS567 is UAS blacklisted by default in kernel > 4.15.x. > Can you check if it still works removing the dedicated hub external > power supply? I've upgraded to 4.15.3, and it does not appear to be blacklisted for uas driver. kernel: usbcore: registered new interface driver usb-storage kernel: scsi host2: uas kernel: usbcore: registered new interface driver uas Full kernel messages upon insertion directly to the computer's USB port (hub not involved at all): https://paste.fedoraproject.org/paste/bPPAl~ngYjktfC--i7NqJA/raw -- Chris Murphy -- 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: JMicron based usb 3.0 to sata enclosure, hangs, numerous errors
2018-02-10 1:00 GMT+01:00 Chris Murphy : > On Fri, Feb 9, 2018 at 3:57 AM, Menion wrote: >> There are multiple reports of UAS issue together with JMS567 (from myself >> also) >> Question: you mentioned that connecting the enclosure to an >> intermediate USB HUB is a workaround. >> Can you specify if your PC USB port is USB 3.0 and if the HUB is USB >> 3.0 as well, and if it is self-powered or not? > > The port and hub are USB 3.0, and the hub has its own power supply (I > guess that's self-powered, not bus powered?). > > [154810.100995] usb 2-4: new SuperSpeed USB device number 11 using xhci_hcd > [154810.353775] usb 2-4: New USB device found, idVendor=2109, idProduct=0812 > [154810.353814] usb 2-4: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [154810.353841] usb 2-4: Product: USB3.0 Hub > [154810.353862] usb 2-4: Manufacturer: VIA Labs, Inc. > [154810.364888] hub 2-4:1.0: USB hub found > [154810.365246] hub 2-4:1.0: 4 ports detected > [154810.465557] usb 1-4: new high-speed USB device number 8 using xhci_hcd > [154810.596631] usb 1-4: New USB device found, idVendor=2109, idProduct=2812 > [154810.596671] usb 1-4: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [154810.596697] usb 1-4: Product: USB2.0 Hub > [154810.596718] usb 1-4: Manufacturer: VIA Labs, Inc. > [154810.605720] hub 1-4:1.0: USB hub found > [154810.606022] hub 1-4:1.0: 4 ports detected > > > > [chris@f27s ~]$ sudo lsusb > Bus 002 Device 011: ID 2109:0812 VIA Labs, Inc. VL812 Hub > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 004: ID 8087:0a2a Intel Corp. > Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > Bus 001 Device 008: ID 2109:2812 VIA Labs, Inc. VL812 Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I'm not sure why there are two instances for this single hub with > lsusb. The verbose output has some differences between the two > instances. > > > -- > Chris Murphy You have two instance because usb 3.0 hubs present themself with an USB 2.0 and USB 3.0 instance, due to the different stack. I wanted to test my enclosure with an hub, but I have just realized that now the JMS567 is UAS blacklisted by default in kernel 4.15.x. Can you check if it still works removing the dedicated hub external power supply? Bye -- 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: JMicron based usb 3.0 to sata enclosure, hangs, numerous errors
On Fri, Feb 9, 2018 at 3:57 AM, Menion wrote: > There are multiple reports of UAS issue together with JMS567 (from myself > also) > Question: you mentioned that connecting the enclosure to an > intermediate USB HUB is a workaround. > Can you specify if your PC USB port is USB 3.0 and if the HUB is USB > 3.0 as well, and if it is self-powered or not? The port and hub are USB 3.0, and the hub has its own power supply (I guess that's self-powered, not bus powered?). [154810.100995] usb 2-4: new SuperSpeed USB device number 11 using xhci_hcd [154810.353775] usb 2-4: New USB device found, idVendor=2109, idProduct=0812 [154810.353814] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [154810.353841] usb 2-4: Product: USB3.0 Hub [154810.353862] usb 2-4: Manufacturer: VIA Labs, Inc. [154810.364888] hub 2-4:1.0: USB hub found [154810.365246] hub 2-4:1.0: 4 ports detected [154810.465557] usb 1-4: new high-speed USB device number 8 using xhci_hcd [154810.596631] usb 1-4: New USB device found, idVendor=2109, idProduct=2812 [154810.596671] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [154810.596697] usb 1-4: Product: USB2.0 Hub [154810.596718] usb 1-4: Manufacturer: VIA Labs, Inc. [154810.605720] hub 1-4:1.0: USB hub found [154810.606022] hub 1-4:1.0: 4 ports detected [chris@f27s ~]$ sudo lsusb Bus 002 Device 011: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 008: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I'm not sure why there are two instances for this single hub with lsusb. The verbose output has some differences between the two instances. -- Chris Murphy -- 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: JMicron based usb 3.0 to sata enclosure, hangs, numerous errors
There are multiple reports of UAS issue together with JMS567 (from myself also) Question: you mentioned that connecting the enclosure to an intermediate USB HUB is a workaround. Can you specify if your PC USB port is USB 3.0 and if the HUB is USB 3.0 as well, and if it is self-powered or not? 2018-02-09 4:17 GMT+01:00 Chris Murphy : > Problem summary: > Out of the box, a USB 3.0 SATA 6.0 enclosure, hangs during reads or > writes and spits out some errors, when directly connected to a > computer's USB port. When connected via a USB hub, uas is still used, > but the errors do not occur. When setting a quirk to blacklist the > drive from uas, the problem doesn't happen when directly connected > either. > > Host: > > Intel ® NUC Board NUC5PPYB > kernel 4.14.18-300.fc27.x86_64 > Fedora 27 > One 1.5A port > Multiple 900 mA ports > > lspci -vvnn > > 00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium > Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] > (rev 21) (prog-if 30 [XHCI]) > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > SERR- Latency: 0 > Interrupt: pin A routed to IRQ 116 > Region 0: Memory at 8140 (64-bit, non-prefetchable) [size=64K] > Capabilities: [70] Power Management version 2 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA > PME(D0-,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Address: fee0300c Data: 4122 > Kernel driver in use: xhci_hcd > > > Enclosure: > > $ sudo lsusb -v > > Bus 002 Device 003: ID 152d:0567 JMicron Technology Corp. / JMicron > USA Technology Corp. JMS567 SATA 6Gb/s bridge > Device Descriptor: > bLength18 > bDescriptorType 1 > bcdUSB 3.00 > bDeviceClass0 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 9 > idVendor 0x152d JMicron Technology Corp. / JMicron USA > Technology Corp. > idProduct 0x0567 JMS567 SATA 6Gb/s bridge > bcdDevice7.01 > iManufacturer 1 JMicron > iProduct2 USB3.0 Device > iSerial 3 DB98765433E84 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 121 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x80 > (Bus Powered) > MaxPower 896mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber0 > 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 > bmAttributes2 > Transfer TypeBulk > 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 > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0400 1x 1024 bytes > bInterval 0 > bMaxBurst 15 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber0 > bAlternateSetting 1 > bNumEndpoints 4 > bInterfaceClass 8 Mass Storage > bInterfaceSubClass 6 SCSI > bInterfaceProtocol 98 > iInterface 10 MSC USB Attached SCSI > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x01 EP 1 OUT > bmAttributes2 > Transfer TypeBulk > 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 0x82 EP 2 IN > bmAttributes2 > Transfer Type
