Seagate 5TB H/D kills the USB 3 port on TX2

The H/D disables the USB 3 port once it was plugged in (via Amazon USB-3 hub or direct connectoin).

The same connection works for WD 4TB H/D. It makes me think that the problem is specific to Seagate H/D (5TB model: SRD0NF1, file type: NTFS).

When plugged the H/D to USB, the light on the H/D blinked a few seconds and turned stable. But the entire USB hub went down the same time. Unplug the hub and plug in any USB device would have no response on the port.

I had to reflash the TX2, and made sure to have a Bluetooth mouse and keyboard connected before trying to duplicate the case on my second Seagate H/D (same model). BTW, the good news is that recovery mode works; while “reset” or reboot maks no difference one the USB port is disabled.

Plug in the second Seagate 5TB H/D, and soon the USB port goes down like the other H/D. Same failure!

If I run “lsusb” command, only two buses are shown after the USB port went down:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The other buses are not shown, which should otherwise be seen normally such as

Bus 002 Device 002: ID 2109:8110 VIA Labs, Inc. Hub

I then plugged the Seagate H/D to a Windows 10 PC. The drive works.

It seems to me the issue is related to compatibility. Ideally, it’d be better to reject a unwanted external device, instead being killed by the device.

I can do another round of debug/rebuild before return the Seagate H/Ds. Please let me know if any idea to bring the USB port back to life.

I think what you really need to share is the log and the detail of board and software.

The TX2 dev kit is old but working, flashed with the latest JetPack.

$ head -n 1 /etc/nv_tegra_release

R32 (release), REVISION: 5.1, GCID: 26202423, BOARD: t186ref, EABI: aarch64, DATE: Fri Feb 19 16:50:29 UTC 2021

$ uname -r
4.9.201-tegra

The failure can be consistently reproduced. Plug in the Seagate H/D (Model: SRD0NF1, 5TB), the system will be frozen for a few seconds, and then the USB 3 port goes down.

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Attached below is the relevant dmesg output:

after-hang (8.5 KB)

And here are the output before xhci halts the host:

[30587.687818] ifidx:0 DHCP - DISCOVER [RX]
[30594.512891] usb 2-1.1: new SuperSpeed USB device number 3 using tegra-xusb
[30594.534229] usb 2-1.1: New USB device found, idVendor=0bc2, idProduct=2344
[30594.534253] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[30594.534269] usb 2-1.1: Product: Portable
[30594.534283] usb 2-1.1: Manufacturer: Seagate
[30594.534296] usb 2-1.1: SerialNumber: NAAZK2E9
[30594.549990] scsi host2: uas
[30594.555080] scsi 2:0:0:0: Direct-Access Seagate Portable 0712 PQ: 0 ANSI: 6
[30603.731104] sd 2:0:0:0: [sda] 9767541167 512-byte logical blocks: (5.00 TB/4.55 TiB)
[30603.738873] sd 2:0:0:0: [sda] 4096-byte physical blocks
[30603.744940] sd 2:0:0:0: [sda] Write Protect is off
[30603.749744] sd 2:0:0:0: [sda] Mode Sense: 53 00 00 08
[30603.750114] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[30603.760237] sd 2:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[30604.896533] sd 2:0:0:0: [sda] tag#7 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD IN
[30604.896562] sd 2:0:0:0: [sda] tag#7 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 07 00 00 00 01 00 00
[30604.896902] sd 2:0:0:0: [sda] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN
[30604.896928] sd 2:0:0:0: [sda] tag#6 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 06 00 00 00 01 00 00
[30604.897207] sd 2:0:0:0: [sda] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN
[30604.897228] sd 2:0:0:0: [sda] tag#5 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 05 00 00 00 01 00 00
[30604.897510] sd 2:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN
[30604.897529] sd 2:0:0:0: [sda] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 04 00 00 00 01 00 00
[30604.897823] sd 2:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN
[30604.897842] sd 2:0:0:0: [sda] tag#3 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 03 00 00 00 01 00 00
[30604.898110] sd 2:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN
[30604.898129] sd 2:0:0:0: [sda] tag#2 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 02 00 00 00 01 00 00
[30604.898389] sd 2:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
[30604.898407] sd 2:0:0:0: [sda] tag#1 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 01 00 00 00 01 00 00
[30604.898667] sd 2:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[30604.898685] sd 2:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00
[30604.898995] scsi host2: uas_eh_bus_reset_handler start
[30604.985153] usb 2-1.1: reset SuperSpeed USB device number 3 using tegra-xusb
[30605.012107] scsi host2: uas_eh_bus_reset_handler success
[30607.868537] sd 2:0:0:0: [sda] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN
[30607.868567] sd 2:0:0:0: [sda] tag#6 CDB: opcode=0x88 88 00 00 00 00 02 46 30 d9 ae 00 00 00 01 00 00
[30607.868902] sd 2:0:0:0: [sda] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN
[30607.868928] sd 2:0:0:0: [sda] tag#5 CDB: opcode=0x88 88 00 00 00 00 02 46 30 d9 ad 00 00 00 01 00 00
[30607.869200] sd 2:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN
[30607.869221] sd 2:0:0:0: [sda] tag#4 CDB: opcode=0x88 88 00 00 00 00 02 46 30 d9 ac 00 00 00 01 00 00
[30607.869496] sd 2:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN
[30607.869515] sd 2:0:0:0: [sda] tag#3 CDB: opcode=0x88 88 00 00 00 00 02 46 30 d9 ab 00 00 00 01 00 00
[30607.869823] scsi host2: uas_eh_bus_reset_handler start
[30608.884403] tegra-xusb 3530000.xhci: controller firmware hang
[30608.890183] tegra-xusb 3530000.xhci: hcd_reinit is disabled or in progress
[30613.040447] tegra-xusb 3530000.xhci: xHCI host not responding to stop endpoint command.

The error log reminds my another thread.

This disk may not follow the usb spec thus need to add to the quirk list.

Thanks for the note.

I’ll return the H/D to Amazon.

Just in case you didn’t know the purpose of the link I posted. This H/D may still work if you put it into the quirk list of the kernel driver. It requires to rebuild the driver so I am not sure if you are willing to do that. It is also ok to get another new one.

See your point. Yeah, I don’t think I want to go down the path of rebuilding the kernel driver for it.

Good to know that. Appreciated.

1 Like