Patriot PXD USB SSD cannot be mount with type-C connector

[LittleBigBrain]

It works fine a few weeks ago. But after recent kernel/driver updates. It stops working. It still works if I connect it to USB 3.1 5000M port. if I connect it to 10000M port, it stops working.

I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart data. But any block operation will fail with remote I/O error: mount, format, dd, etc

The port is find, I connected other device to it, it is still working without issue. The USB controller and storage device are:
```
USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory
```

kernel
```
5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
```
The dmesg:
```
[ 841.199638] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd
[ 841.220480] usb 2-2: New USB device found, idVendor=13fe, idProduct=2570, bcdDevice=52.04
[ 841.220485] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 841.220489] usb 2-2: Product: Patriot Memory
[ 841.220492] usb 2-2: Manufacturer: PXD
[ 841.220495] usb 2-2: SerialNumber: 5112005142442DD3000019
[ 841.249317] usbcore: registered new interface driver usb-storage
[ 841.257779] scsi host1: uas
[ 841.257877] usbcore: registered new interface driver uas
[ 841.258567] scsi 1:0:0:0: Direct-Access PXD Patriot Memory 5204 PQ: 0 ANSI: 6
[ 841.259142] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 843.227753] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB)
[ 843.227754] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[ 843.227876] sd 1:0:0:0: [sdb] Write Protect is off
[ 843.227877] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08
[ 843.228071] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 843.228272] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[ 843.270539] sdb: sdb1 sdb2
[ 843.271928] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 906.555686] systemd-journald[516]: Successfully sent stream file descriptor to service manager.
[ 1022.377340] systemd-journald[516]: Successfully sent stream file descriptor to service manager.
[ 1224.144553] sd 1:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1224.144560] sd 1:0:0:0: [sdb] tag#5 Sense Key : Hardware Error [current]
[ 1224.144562] sd 1:0:0:0: [sdb] tag#5 ASC=0x44 <<vendor>>ASCQ=0x99
[ 1224.144564] sd 1:0:0:0: [sdb] tag#5 CDB: Read(10) 28 00 00 06 40 00 00 00 01 00
[ 1224.144567] blk_update_request: critical target error, dev sdb, sector 409600 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0
[ 1224.144588] XFS (sdb1): SB validate failed with error -121.
[ 1272.199769] systemd-journald[516]: Successfully sent stream file descriptor to service manager.

```

The kernel log:
```
Sep 6 11:35:22 kernel: [ 841.199638] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd
Sep 6 11:35:22 kernel: [ 841.220480] usb 2-2: New USB device found, idVendor=13fe, idProduct=2570, bcdDevice=52.04
Sep 6 11:35:22 kernel: [ 841.220485] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 6 11:35:22 kernel: [ 841.220489] usb 2-2: Product: Patriot Memory
Sep 6 11:35:22 kernel: [ 841.220492] usb 2-2: Manufacturer: PXD
Sep 6 11:35:22 kernel: [ 841.220495] usb 2-2: SerialNumber: 5112005142442DD3000019
Sep 6 11:35:22 kernel: [ 841.249317] usbcore: registered new interface driver usb-storage
Sep 6 11:35:22 kernel: [ 841.257779] scsi host1: uas
Sep 6 11:35:22 kernel: [ 841.257877] usbcore: registered new interface driver uas
Sep 6 11:35:22 kernel: [ 841.258567] scsi 1:0:0:0: Direct-Access PXD Patriot Memory 5204 PQ: 0 ANSI: 6
Sep 6 11:35:22 kernel: [ 841.259142] sd 1:0:0:0: Attached scsi generic sg1 type 0
Sep 6 11:35:24 kernel: [ 843.227753] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB)
Sep 6 11:35:24 kernel: [ 843.227754] sd 1:0:0:0: [sdb] 4096-byte physical blocks
Sep 6 11:35:24 kernel: [ 843.227876] sd 1:0:0:0: [sdb] Write Protect is off
Sep 6 11:35:24 kernel: [ 843.227877] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08
Sep 6 11:35:24 kernel: [ 843.228071] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 6 11:35:24 kernel: [ 843.228272] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
Sep 6 11:35:24 kernel: [ 843.270539] sdb: sdb1 sdb2
Sep 6 11:35:24 kernel: [ 843.271928] sd 1:0:0:0: [sdb] Attached SCSI disk
Sep 6 11:41:45 kernel: [ 1224.144553] sd 1:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 6 11:41:45 kernel: [ 1224.144560] sd 1:0:0:0: [sdb] tag#5 Sense Key : Hardware Error [current]
Sep 6 11:41:45 kernel: [ 1224.144562] sd 1:0:0:0: [sdb] tag#5 ASC=0x44 <<vendor>>ASCQ=0x99
Sep 6 11:41:45 kernel: [ 1224.144564] sd 1:0:0:0: [sdb] tag#5 CDB: Read(10) 28 00 00 06 40 00 00 00 01 00
Sep 6 11:41:45 kernel: [ 1224.144567] blk_update_request: critical target error, dev sdb, sector 409600 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0
Sep 6 11:41:45 kernel: [ 1224.144588] XFS (sdb1): SB validate failed with error -121.
```

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1894104

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Matthew Ruffell (mruffell)]

@braingateway

Can you please try booting into the 5.4.0-42-generic kernel and see if that works?

When you turn your computer on, press and hold the shift key to access the GRUB boot menu.
Select "Advanced Options" and then "Ubuntu, with Linux 5.4.0-42-generic"

If 5.4.0-42-generic works and 5.4.0-45-generic doesn't, then we broke something, and we will likely need to bisect to find the fix.

[LittleBigBrain (braingateway)]

@Matthew

I boot int o 5.4.0-42, it has different symptom, now the `udisksctl mount -b /dev/sdb1` halt for more than 10 mins and the dmesg is different, it does not error out immediately, but repetitively reset the handle.

[ 83.317249] systemd-journald[597]: Successfully sent stream file descriptor to service manager.
[ 92.750180] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd
[ 92.775135] usb 2-2: New USB device found, idVendor=13fe, idProduct=2570, bcdDevice=52.04
[ 92.775140] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 92.775144] usb 2-2: Product: Patriot Memory
[ 92.775146] usb 2-2: Manufacturer: PXD
[ 92.775148] usb 2-2: SerialNumber: 5112005142442DD3000019
[ 92.804959] usbcore: registered new interface driver usb-storage
[ 92.813302] scsi host1: uas
[ 92.813411] usbcore: registered new interface driver uas
[ 92.813813] scsi 1:0:0:0: Direct-Access PXD Patriot Memory 5204 PQ: 0 ANSI: 6
[ 92.814407] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 94.784086] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB)
[ 94.784092] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[ 94.784246] sd 1:0:0:0: [sdb] Write Protect is off
[ 94.784251] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08
[ 94.784492] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 94.784850] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[ 94.811392] sdb: sdb1 sdb2
[ 94.814205] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 114.748031] systemd-journald[597]: Successfully sent stream file descriptor to service manager.
[ 220.511826] XFS (sdb1): Mounting V5 Filesystem
[ 251.324415] sd 1:0:0:0: [sdb] tag#7 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
[ 251.324424] sd 1:0:0:0: [sdb] tag#7 CDB: Write(10) 2a 00 06 46 41 10 00 04 00 00
[ 251.328955] sd 1:0:0:0: [sdb] tag#6 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT
[ 251.328962] sd 1:0:0:0: [sdb] tag#6 CDB: Write(10) 2a 00 06 46 4d 10 00 04 00 00
[ 251.336191] sd 1:0:0:0: [sdb] tag#5 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT
[ 251.336200] sd 1:0:0:0: [sdb] tag#5 CDB: Write(10) 2a 00 06 46 49 10 00 04 00 00
[ 251.343184] sd 1:0:0:0: [sdb] tag#4 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT
[ 251.343192] sd 1:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 06 46 45 10 00 04 00 00
[ 251.392372] scsi host1: uas_eh_device_reset_handler start
[ 251.521091] usb 2-2: reset SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd
[ 251.545897] scsi host1: uas_eh_device_reset_handler success
[ 269.017285] systemd-journald[597]: Successfully sent stream file descriptor to service manager.
[ 282.052398] scsi host1: uas_eh_device_reset_handler start
[ 282.080099] sd 1:0:0:0: [sdb] tag#27 uas_zap_pending 0 uas-tag 1 inflight: CMD
[ 282.080102] sd 1:0:0:0: [sdb] tag#27 CDB: Write(10) 2a 00 06 46 45 10 00 04 00 00
[ 282.080104] sd 1:0:0:0: [sdb] tag#24 uas_zap_pending 0 uas-tag 2 inflight: CMD
[ 282.080106] sd 1:0:0:0: [sdb] tag#24 CDB: Write(10) 2a 00 06 46 49 10 00 04 00 00
[ 282.080107] sd 1:0:0:0: [sdb] tag#...

[LittleBigBrain (braingateway)]

and I am pretty sure it worked on older kernel a few weeks ago. It is a brand new device, I just formated it and backed up files onto it a few weeks ago. Unfortunately I do not have older kernel than 5.4.0-42

[Matthew Ruffell (mruffell)]

How about you try a slightly older kernel then:

To install 5.4.0-31-generic:

$ sudo apt install linux-image-5.4.0-31-generic linux-modules-5.4.0-31-generic linux-modules-extra-5.4.0-31-generic linux-headers-5.4.0-31-generic linux-headers-5.4.0-31

Then reboot your computer. Do the same as you did to access 5.4.0-42-generic. Press the Shift key, go into Advanced Options, then boot 5.4.0-31-generic.

See if it works there.

If it does, then we know that something changed between 5.4.0-31-generic and 5.4.0-42 or -45 generic.

Once you have tried 5.4.0-31-generic, if you want to remove it, run:

$ sudo apt remove linux-image-5.4.0-31-generic linux-modules-5.4.0-31-generic linux-modules-extra-5.4.0-31-generic linux-headers-5.4.0-31-generic linux-headers-5.4.0-31

Let me know how it goes.