USB 3 devices are not detected on thunderbolt 3

Bug #1830930 reported by Toby Broom
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I found a strange problem when trying to connect my Samsung T5 SSD.

If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues.

If I unplug it and reconnect then it's not detected.

If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg.

If I connect the device using another cable then it also doesn't work

I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues.

Ubuntu 19.04, 5.0.0-15-generic

04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06)
3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06)

---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: toby 1495 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2019-04-27 (31 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 8087:0aaa Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP EliteDesk 800 G4 DM 65W
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-15-generic N/A
 linux-backports-modules-5.0.0-15-generic N/A
 linux-firmware 1.178.1
Tags: disco
Uname: Linux 5.0.0-15-generic x86_64
UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/15/2019
dmi.bios.vendor: HP
dmi.bios.version: Q21 Ver. 02.06.03
dmi.board.name: 845A
dmi.board.vendor: HP
dmi.board.version: KBC Version 07.D2.00
dmi.chassis.asset.tag: 8CC84321CJ
dmi.chassis.type: 6
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr:
dmi.product.family: 103C_53307F HP EliteDesk
dmi.product.name: HP EliteDesk 800 G4 DM 65W
dmi.product.sku: 5BA07US#ABA
dmi.sys.vendor: HP

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1830930/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Toby Broom (ytterbium)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Toby Broom (ytterbium) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected disco
description: updated
Revision history for this message
Toby Broom (ytterbium) wrote : CRDA.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : IwConfig.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : Lspci.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : ProcEnviron.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : ProcModules.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : PulseList.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : RfKill.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : UdevDb.txt

apport information

Revision history for this message
Toby Broom (ytterbium) wrote : WifiSyslog.txt

apport information

Toby Broom (ytterbium)
affects: linux (Ubuntu) → thunderbolt-tools (Ubuntu)
Revision history for this message
Mario Limonciello (superm1) wrote :

With most machines they have a security level set in BIOS. The default security level means you need to authorize the thunderbolt device using bolt or thunderbolt-tools, did you do that?

Revision history for this message
Toby Broom (ytterbium) wrote :

I set the BIOS to no security and still have the same effect.

A USB device on thunderbolt bus should not need authorization? On windows I never saw that and also in Linux with the USB 2 cable there was no need to authorize.

The Thunderbolt controller is authorized though.

I'm not sure the correct place is under thunderbolt, it's seems more like a hardware detection bug?

Revision history for this message
Yehezkel Bernat (yehezkelshb) wrote :

From https://www.samsung.com/semiconductor/minisite/ssd/product/portable/t5/ I learn this is a USB 3.1 Gen2 device, not a Thunderbolt device, so authorization isn't relevant (and thunderbolt-tools isn't the relevant package).

Still, the fact that you had to force power the controller even when a device is connected (and especially as it works when it's connected on boot) suggests there is some sort of issue between the BIOS / port controller / cable / maybe other parts in the system that take part in the HW detection.

Revision history for this message
Yehezkel Bernat (yehezkelshb) wrote :

I guess it worth updating your BIOS to the latest version.
According to the details above you have Ver. 02.06.03, while in HP site I can find Ver 02.07.00
The release notes there mention several fixes for the handling of USB-C ports.

(I hope there is an easy way to do so on Linux. Hopefully it's available from fwupd :) )

https://support.hp.com/us-en/drivers/selfservice/hp-elitedesk-800-65w-g4-desktop-mini-pc/21353734

Revision history for this message
Toby Broom (ytterbium) wrote :

I'll give it a go and move it

affects: thunderbolt-tools (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Toby Broom (ytterbium) wrote :

BIOS update didn't change anything, I guess maybe it's not even a Linux problem it's an HP problem. I could install windows to test if it work there as crosscheck with hardware vs software.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Yes, please test it under Windows. And don't forget to upgrade Thunderbolt firmware before switching back to Linux.

Revision history for this message
Toby Broom (ytterbium) wrote :

I got a different USB 3.1 SSD and this works fine so it seems a real edge case that Samsung SSD does not work on this TB controller. I can test with windows soon

Revision history for this message
Toby Broom (ytterbium) wrote :

It's the same in windows so must be a hardware problem with HP.

Revision history for this message
Toby Broom (ytterbium) wrote :

Looks like hardware issue.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.