[iotg][tgl-up3]Desktop does not recognize insertion of USB3 drive

[Doug Jacobs]

[Summary]
Installed iotg-focal-desktop-20210813.img
Need to generate a CID for this system.
Insert USB drive, named Jumpdrive, into USB3 port with the initial-test tool on it.
(keyboard is inserted into the USB2.0 port)
/media is empty. Usually I would be able to go to /media/u/Jumpdrive

Keyboard works, USB drive is not recognized by this system.
Other systems have no problems recognizing the USB drive and mounting Jumpdrive.

[Steps to reproduce]
Insert USB drive into USB3 port
Use terminal to cd /media

[Expected result]
Should see the drive under /media/u/Jumpdrive

[Actual result]
/media is empty.

[Failure rate] 100%

[Additional information]
CID: NONE
SKU:
system-manufacturer: Intel Corporation
system-product-name: Tiger Lake Client Platform
bios-version: TGLIFUI1.R00.3455.A02.2011240812
CPU: 11th Gen Intel(R) Core(TM) i5-1145GRE @ 2.60GHz (8x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a49] (rev 01)
kernel-version: 5.11.0-1012-intel

[Stage]
Issue reported and logs collected right after it happened

[Doug Jacobs (djacobs98)]

Automatically attached

[Doug Jacobs (djacobs98)]

Automatically attached

[Doug Jacobs (djacobs98)]

Automatically attached

[Alex Hung (alexhung)]

When a USB drive is inserted, dmesg shows corresponding messages as below (an example on my computer):

[187654.189048] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[187654.215104] usb 2-1: New USB device found, idVendor=125f, idProduct=312b, bcdDevice=11.00
[187654.215118] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[187654.215124] usb 2-1: Product: ADATA USB Flash Drive
[187654.215129] usb 2-1: Manufacturer: ADATA
[187654.215133] usb 2-1: SerialNumber: 1471010191240006
[187654.222531] usb-storage 2-1:1.0: USB Mass Storage device detected
[187654.223284] scsi host4: usb-storage 2-1:1.0
[187655.395986] scsi 4:0:0:0: Direct-Access ADATA USB Flash Drive 1100 PQ: 0 ANSI: 6
[187655.396263] sd 4:0:0:0: Attached scsi generic sg1 type 0
[187655.397184] sd 4:0:0:0: [sdb] 60620800 512-byte logical blocks: (31.0 GB/28.9 GiB)
[187655.397819] sd 4:0:0:0: [sdb] Write Protect is off
[187655.397822] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
[187655.398398] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[187655.435760] sdb: sdb1
[187655.438211] sd 4:0:0:0: [sdb] Attached SCSI removable disk

[Alex Hung (alexhung)]

If there is something wrong, dmesg shows the error (an example as below):

[187848.279545] usb 3-1.2.1: new high-speed USB device number 8 using xhci_hcd
[187848.382985] usb 3-1.2.1: New USB device found, idVendor=0930, idProduct=6545, bcdDevice= 1.10
[187848.383000] usb 3-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[187848.383007] usb 3-1.2.1: Product: TransMemory
[187848.383012] usb 3-1.2.1: Manufacturer: TOSHIBA
[187848.383016] usb 3-1.2.1: SerialNumber: 000FEA0AB9F5B920A41500D8
[187848.386366] usb-storage 3-1.2.1:1.0: USB Mass Storage device detected
[187848.386936] scsi host5: usb-storage 3-1.2.1:1.0
[187849.441367] scsi 5:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 0 CCS
[187849.442289] sd 5:0:0:0: Attached scsi generic sg2 type 0
[187849.800922] sd 5:0:0:0: [sdc] 15687680 512-byte logical blocks: (8.03 GB/7.48 GiB)
[187849.801283] sd 5:0:0:0: [sdc] Write Protect is off
[187849.801292] sd 5:0:0:0: [sdc] Mode Sense: 23 00 00 00
[187849.801654] sd 5:0:0:0: [sdc] No Caching mode page found
[187849.801664] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[187849.861053] sdc: sdc1
[187849.864038] sd 5:0:0:0: [sdc] Attached SCSI removable disk
[187851.792606] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

[Alex Hung (alexhung)]

In kern.log in #3, there are related messages like below, and everything looks normal. It is not certain whether this USB drive is the one in question.

Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.138339] usb 4-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.159621] usb 4-2: New USB device found, idVendor=21c4, idProduct=0809, bcdDevice=11.00
Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.159629] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.159632] usb 4-2: Product: USB Flash Drive
Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.159635] usb 4-2: Manufacturer: Lexar
Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.159637] usb 4-2: SerialNumber: 54000010282OSANR
Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.236604] usb-storage 4-2:1.0: USB Mass Storage device detected
Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.236844] scsi host0: usb-storage 4-2:1.0
Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.237000] usbcore: registered new interface driver usb-storage
Sep 7 02:34:41 u-Tiger-Lake-Client-Platform kernel: [15664.239631] usbcore: registered new interface driver uas
Sep 7 02:34:42 u-Tiger-Lake-Client-Platform kernel: [15665.301655] scsi 0:0:0:0: Direct-Access Lexar USB Flash Drive 1100 PQ: 0 ANSI: 6
Sep 7 02:34:42 u-Tiger-Lake-Client-Platform kernel: [15665.302018] sd 0:0:0:0: Attached scsi generic sg0 type 0
Sep 7 02:34:42 u-Tiger-Lake-Client-Platform kernel: [15665.302879] sd 0:0:0:0: [sda] 243404800 512-byte logical blocks: (125 GB/116 GiB)
Sep 7 02:34:42 u-Tiger-Lake-Client-Platform kernel: [15665.303050] sd 0:0:0:0: [sda] Write Protect is off
Sep 7 02:34:42 u-Tiger-Lake-Client-Platform kernel: [15665.303053] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Sep 7 02:34:42 u-Tiger-Lake-Client-Platform kernel: [15665.303183] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 7 02:34:42 u-Tiger-Lake-Client-Platform kernel: [15665.327622] sda: sda1
Sep 7 02:34:42 u-Tiger-Lake-Client-Platform kernel: [15665.328903] sd 0:0:0:0: [sda] Attached SCSI removable disk

Please boot a system, insert the "Jumpdrive", and upload dmesg log file.

[Doug Jacobs (djacobs98)]

This system soon became unusable due to the BIOS becoming corrupted after turning off TPM and needed to be reflashed. This USB issue is a symptom of that corruption.

The system worked normally after reflashing with the newest BIOS.