Re: [Workaround] ASM1153E : ASM 174c:55aa problems re-loaded [quirk needed]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 13-11-15 20:12, Manfred_Knick wrote:
First of all:
A big "Thank You!" especially to Sarah Sharp and Hans de Goede.
Finding their contributions finally led my way.

Second:
Please, keep me CC'ed on this subject - I am not subscribed to the list above.

####################################################################################################################
HARDWARE involved:
##################

- Xeon E3-1276 v3

- Asus P9D WS
- - 00:14.0 USB controller [0c03] :
- - Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05)

- LC-Power "LC-35U3-Becrux"    with
- - ASM1153E                   soldered onto its adapter board                  <-- <--
- - - 130926 a1 00 00          original firmware version
- - - 140509_A1_82_80.bin      newest firmware update I could gather from
- - -                          http://plugable.com/drivers/hddockfirmware

- Seagate Barracuda 7200.11 1.5TB (ST315003 41AS)

####################################################################################################################
Kernel versions involved:
#########################

- linux-4.1.12-gentoo                                            <-- failure, as described below
- linux-4.1.13-gentoo                                            <-- failure

- linux-4.2.6-gentoo                                             <-- failure

- linux-4.3.0-gentoo                                             <-- failure
- linux-4.3.0-gentoo   with   "usb-storage.quirks=174c:55aa:u"   <-- working  [Workaround]

####################################################################################################################
SHORT STORY:
############

ASM continues shuffling new HW under the old hat of 174c:55aa.

Connecting the external enclosure, lsusb identifies it as "ASM1051 SATA 3Gb/s bridge" -
you need a microscope to finally detect the chip as an ASM1153E instead.

Thanks for checking the exact bridge chip model.

Usage of the device @ USB 2 succeeds.

"Normal" usage of the device @ USB 3 succeeds, but
under stress the connection fails *instantaneusly* .

Adding "usb-storage.quirks=174c:55aa:u" to the kernel start parameters
makes the device fall back from UAS to usb-storage,
but deliver stable full throughput the disc is capable of.

####################################################################################################################
LONG  STORY:
############

[ 5155.065761] usb 2-6: new SuperSpeed USB device number 2 using xhci_hcd
[ 5155.077463] usb 2-6: New USB device found, idVendor=174c, idProduct=55aa
[ 5155.077467] usb 2-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 5155.077469] usb 2-6: Product: mkn_LC-53U3-Becrux
[ 5155.077470] usb 2-6: Manufacturer: mkn_LC-POWER
[ 5155.077472] usb 2-6: SerialNumber: 201401000056

[ 5155.079306] scsi host7: uas
[ 5155.163597] scsi 7:0:0:0: Direct-Access     ST315003 41AS             0    PQ: 0 ANSI: 6

[ 5155.163966] sd 7:0:0:0: Attached scsi generic sg6 type 0
[ 5155.164117] sd 7:0:0:0: [sdd] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
[ 5155.164433] sd 7:0:0:0: [sdd] Write Protect is off
[ 5155.164435] sd 7:0:0:0: [sdd] Mode Sense: 43 00 00 00
[ 5155.164553] sd 7:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5155.229663]  sdd: sdd1
[ 5155.230384] sd 7:0:0:0: [sdd] Attached SCSI disk

### Until here, everything is o.k.

### Afterwards, "normal" / "slow" access to the disk works o.k.

### But when stressing the disk (even without mounting a fs, e.g. with "dd"),
### a READ ERROR occurs right away:

[ 7505.098336] sd 7:0:0:0: [sdd] tag#0 data cmplt err -71 uas-tag 1 inflight: CMD
[ 7505.098341] sd 7:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 0e df 25 d0 00 01 00 00

This indicates a usb-3 signalling error, have you tried replacing the USB-3
cable. Preferably with a high quality usb-3 cable ?

[ 7505.101696] xhci_hcd 0000:00:14.0: ERROR Transfer event for disabled endpoint or incorrect stream ring    <-- !!!
[ 7505.101708] xhci_hcd 0000:00:14.0: @00000000ffffc6d0 00000000 00000000 04000000 01038000

This is sorta kinda normal once things have failed (not really, but it happens).

[ 7535.253307] sd 7:0:0:0: [sdd] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
[ 7535.253311] sd 7:0:0:0: [sdd] tag#1 CDB: Read(10) 28 00 0e df 26 d0 00 01 00 00
[ 7535.253343] sd 7:0:0:0: [sdd] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[ 7535.253344] sd 7:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 0e df 25 d0 00 01 00 00

[ 7535.253363] scsi host7: uas_eh_bus_reset_handler start
[ 7535.355461] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[ 7535.367384] scsi host7: uas_eh_bus_reset_handler success

# From now on, the connection to the disk is lost:

[ 7542.276188] sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 7542.276193] sd 7:0:0:0: [sdd] tag#0 Sense Key : Not Ready [current]
[ 7542.276196] sd 7:0:0:0: [sdd] tag#0 Add. Sense: Medium not present                                        <-- !!!
[ 7542.276198] sd 7:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 0e df 26 d0 00 01 00 00
[ 7542.276200] blk_update_request: I/O error, dev sdd, sector 249505488

### < ... iterated ... >

### Power-OFF / Power-ON  the USB Disk:

[12629.885763] usb 2-6: new SuperSpeed USB device number 3 using xhci_hcd
[12629.897417] usb 2-6: New USB device found, idVendor=174c, idProduct=55aa
[12629.897422] usb 2-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[12629.897424] usb 2-6: Product: mkn_LC-53U3-Becrux
[12629.897426] usb 2-6: Manufacturer: mkn_LC-POWER
[12629.897428] usb 2-6: SerialNumber: 201401000056
[12629.898921] scsi host8: uas
[12629.976381] scsi 8:0:0:0: Direct-Access     ST315003 41AS             0    PQ: 0 ANSI: 6
[12629.976686] sd 8:0:0:0: Attached scsi generic sg6 type 0
[12629.976788] sd 8:0:0:0: [sde] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
[12629.977105] sd 8:0:0:0: [sde] Write Protect is off
[12629.977108] sd 8:0:0:0: [sde] Mode Sense: 43 00 00 00
[12629.977222] sd 8:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[12630.035392]  sde: sde1
[12630.036222] sd 8:0:0:0: [sde] Attached SCSI disk
[12634.107292] usb 2-6: USB disconnect, device number 3
[12634.107829] sd 8:0:0:0: [sde] Synchronizing SCSI cache
[12634.199253] sd 8:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[12634.405237] usb 2-6: new SuperSpeed USB device number 4 using xhci_hcd
[12634.416877] usb 2-6: New USB device found, idVendor=174c, idProduct=55aa
[12634.416882] usb 2-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[12634.416885] usb 2-6: Product: mkn_LC-53U3-Becrux
[12634.416888] usb 2-6: Manufacturer: mkn_LC-POWER
[12634.416890] usb 2-6: SerialNumber: 201401000056
[12634.418494] scsi host9: uas
[12634.418899] scsi 9:0:0:0: Direct-Access     ST315003 41AS             0    PQ: 0 ANSI: 6
[12634.419429] sd 9:0:0:0: Attached scsi generic sg6 type 0
[12634.419514] sd 9:0:0:0: [sde] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
[12634.419840] sd 9:0:0:0: [sde] Write Protect is off
[12634.419847] sd 9:0:0:0: [sde] Mode Sense: 43 00 00 00
[12634.419999] sd 9:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[12634.447456]  sde: sde1
[12634.448233] sd 9:0:0:0: [sde] Attached SCSI disk

### NOTABENE: Now it's a 'new' disk _sde_ , not _sdd_ any more

### Stressing disc access with "dd if=/dev/sde of=/dev/zero" results in same failure right away:

[13492.949113] sd 9:0:0:0: [sde] tag#0 data cmplt err -71 uas-tag 1 inflight: CMD
[13492.949117] sd 9:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 00 08 c6 e0 00 01 00 00
[13492.952418] xhci_hcd 0000:00:14.0: ERROR Transfer event for disabled endpoint or incorrect stream ring    <-- !!!
[13492.952430] xhci_hcd 0000:00:14.0: @00000000ffffc320 00000000 00000000 04000000 03038001

[13523.257665] sd 9:0:0:0: [sde] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
[13523.257669] sd 9:0:0:0: [sde] tag#1 CDB: Read(10) 28 00 00 08 c7 e0 00 01 00 00
[13523.257700] sd 9:0:0:0: [sde] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[13523.257702] sd 9:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 00 08 c6 e0 00 01 00 00

[13523.257721] scsi host9: uas_eh_bus_reset_handler start
[13523.359827] usb 2-6: reset SuperSpeed USB device number 4 using xhci_hcd
[13523.372038] scsi host9: uas_eh_bus_reset_handler success

[13530.309911] sd 9:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[13530.309917] sd 9:0:0:0: [sde] tag#0 Sense Key : Not Ready [current]
[13530.309919] sd 9:0:0:0: [sde] tag#0 Add. Sense: Medium not present                                        <-- !!!
[13530.309921] sd 9:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 00 08 c7 e0 00 01 00 00
[13530.309923] blk_update_request: I/O error, dev sde, sector 575456

### < ... iterated ... >

####################################################################################################################
WORKAROUND :
############

### Modified my /boot/grub/grub.conf :
###
###       linux /vmlinuz-4.3.0-gentoo ... usb-storage.quirks=174c:55aa:u                                    <-- !!!

[   79.892893] usb 2-6: new SuperSpeed USB device number 2 using xhci_hcd
[   79.904640] usb 2-6: New USB device found, idVendor=174c, idProduct=55aa
[   79.904648] usb 2-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[   79.904653] usb 2-6: Product: mkn_LC-53U3-Becrux
[   79.904657] usb 2-6: Manufacturer: mkn_LC-POWER
[   79.904660] usb 2-6: SerialNumber: 201401000056

[   79.905574] usb 2-6: UAS is blacklisted for this device, using usb-storage instead                        <-- !!!
[   79.906001] usb 2-6: UAS is blacklisted for this device, using usb-storage instead                        <-- !!!

[   79.906010] usb-storage 2-6:1.0: USB Mass Storage device detected

[   79.906147] usb-storage 2-6:1.0: Quirks match for vid 174c pid 55aa: c00000                               <-- !!!

[   79.906215] scsi host7: usb-storage 2-6:1.0
[   80.965177] scsi 7:0:0:0: Direct-Access     ST315003 41AS             0    PQ: 0 ANSI: 6
[   80.965294] sd 7:0:0:0: Attached scsi generic sg6 type 0
[   80.965475] sd 7:0:0:0: [sdd] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
[   80.965657] sd 7:0:0:0: [sdd] Write Protect is off
[   80.965658] sd 7:0:0:0: [sdd] Mode Sense: 43 00 00 00
[   80.965858] sd 7:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   80.990135]  sdd: sdd1
[   80.991087] sd 7:0:0:0: [sdd] Attached SCSI disk
[  180.683067] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd

### Stressing disc access with "dd if=/dev/sde of=/dev/zero" :
###
### SUCCESS : on-going transfer rates of ~ 125 MB/s right from the beginning
###           which is the maximum a Seagate Barracuda 7200.11 1.5TB (ST31500341AS) can supply.
###
### NO failure any more :
###           the whole disk (all of the 1.5 TB) was "read" (dd) successfully in one go.


### But now in dmesg :

[  180.683067] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[  199.004752] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[  206.422149] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[  219.712569] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[  230.824786] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[  241.110217] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[  248.015814] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd

### < ... iterated 953 times ... >

Right so things are still not good, but the usb-storage's driver error recovery
seems to be doing a better job of hobbling along, but clearly there is still
an issue if you get 953 resets (a reset is done by the usb-storage driver on an
unrecoverable error).

My suggestions:

-Check your usb-3 cable, replace it with a high quality one, and try to get a short
 (ish) cable, usb-3 does not do long cables well.

-Check you enclosure's power-supply, according to this:
 http://www.seagate.com/staticfiles/support/disc/manuals/desktop/Barracuda%207200.11/100507013c.pdf

 Your disk is rated for a peak current of 2.8A, how much Amps does the power-brick which
 comes with the enclosure deliver?




### latest:

Nov 13 17:23:21 sid kernel: usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd

####################################################################################################################
Another suspicion:
##################

### perhaps unrelated : ( I did not pull any jack at all )

Nov 13 18:04:27 sid root[10810]: ACPI event unhandled: jack/lineout LINEOUT plug
Nov 13 18:04:27 sid root[10814]: ACPI event unhandled: jack/videoout VIDEOOUT plug

Nov 13 18:19:34 sid root[11144]: ACPI event unhandled: jack/lineout LINEOUT unplug
Nov 13 18:19:34 sid root[11147]: ACPI event unhandled: jack/videoout VIDEOOUT unplug

Nov 13 18:19:47 sid root[11152]: ACPI event unhandled: jack/lineout LINEOUT plug
Nov 13 18:19:47 sid root[11156]: ACPI event unhandled: jack/videoout VIDEOOUT plug

### this is now almost 1 h later:

Nov 13 18:19:47 sid kernel: usb 2-6: USB disconnect, device number 2                               <-- !!!
Nov 13 18:19:47 sid kernel: sd 7:0:0:0: [sdd] Synchronizing SCSI cache
Nov 13 18:19:47 sid kernel: sd 7:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK

### followed by a "new" connect (which was defenitely not initiated by me) :

Nov 13 18:19:48 sid kernel: usb 2-6: new SuperSpeed USB device number 3 using xhci_hcd
Nov 13 18:19:48 sid kernel: usb 2-6: New USB device found, idVendor=174c, idProduct=55aa
Nov 13 18:19:48 sid kernel: usb 2-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Nov 13 18:19:48 sid kernel: usb 2-6: Product: mkn_LC-53U3-Becrux
Nov 13 18:19:48 sid kernel: usb 2-6: Manufacturer: mkn_LC-POWER
Nov 13 18:19:48 sid kernel: usb 2-6: SerialNumber: 201401000056
Nov 13 18:19:48 sid kernel: usb 2-6: UAS is blacklisted for this device, using usb-storage instead
Nov 13 18:19:48 sid kernel: usb 2-6: UAS is blacklisted for this device, using usb-storage instead
Nov 13 18:19:48 sid kernel: usb-storage 2-6:1.0: USB Mass Storage device detected
Nov 13 18:19:48 sid kernel: usb-storage 2-6:1.0: Quirks match for vid 174c pid 55aa: c00000
Nov 13 18:19:48 sid kernel: scsi host8: usb-storage 2-6:1.0
Nov 13 18:19:49 sid kernel: scsi 8:0:0:0: Direct-Access     ST315003 41AS             0    PQ: 0 ANSI: 6
Nov 13 18:19:49 sid kernel: sd 8:0:0:0: Attached scsi generic sg6 type 0
Nov 13 18:19:49 sid kernel: sd 8:0:0:0: [sdd] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
Nov 13 18:19:49 sid kernel: sd 8:0:0:0: [sdd] Write Protect is off
Nov 13 18:19:49 sid kernel: sd 8:0:0:0: [sdd] Mode Sense: 43 00 00 00
Nov 13 18:19:49 sid kernel: sd 8:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 13 18:19:49 sid kernel:  sdd: sdd1
Nov 13 18:19:49 sid kernel: sd 8:0:0:0: [sdd] Attached SCSI disk

### This correlates to the fact that under Windows 8.1 / USB 2.0,
### the disk also magically disconnects after some time;
### only mechanism to "re-awake" I found so far was POWER-OFF / - ON

Right this sounds more and more (with the disconnects) like a bad cable
and/or power supply problem to me.

Regards,

Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux