Activity log for bug #1894104

Date Who What changed Old value New value Message
2020-09-03 13:07:35 LittleBigBrain bug added bug
2020-09-03 13:09:04 LittleBigBrain description It works fine a few weeks ago. But after recent kernel/driver updates. It stop working. It still work if I connect it to USB 3.1 5000M port. if I connect it to 10000M port, it stop 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 ``` It works fine a few weeks ago. But after recent kernel/driver updates. It stop working. It still work if I connect it to USB 3.1 5000M port. if I connect it to 10000M port, it stop 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 ```
2020-09-03 13:10:19 LittleBigBrain description It works fine a few weeks ago. But after recent kernel/driver updates. It stop working. It still work if I connect it to USB 3.1 5000M port. if I connect it to 10000M port, it stop 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 ``` 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 ```
2020-09-03 13:30:11 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2020-09-03 13:30:12 Ubuntu Kernel Bot tags focal
2020-09-03 23:16:19 Matthew Ruffell nominated for series Ubuntu Focal
2020-09-03 23:16:19 Matthew Ruffell bug task added linux (Ubuntu Focal)
2020-09-03 23:16:31 Matthew Ruffell bug added subscriber Matthew Ruffell
2020-09-06 10:23:40 LittleBigBrain description 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 ``` 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. ```