Linux USB
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216728] Thunderbolt USB Controller died after resume on Intel CometLake platform
Date: Sun, 20 Sep 2026 15:06:00 +0000	[thread overview]
Message-ID: <bug-216728-208809-QFGirDJmzU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216728-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216728

Ondřej Soldát (darnexus.04@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darnexus.04@gmail.com

--- Comment #49 from Ondřej Soldát (darnexus.04@gmail.com) ---
I am facing similar issue on ThinkPad X390 Yoga running CachyOS when plugging
USB-C flash drive directly into Thunderbolt port. When plugged into the same
port using dock the issue does not occur.

Component: USB
Hardware: Intel (Titan Ridge JHL7540, 8086:15c1)
Kernel version tested: 7.2.6 (mainline/cachyos), 6.18.52 (LTS/cachyos)
Regression: Unknown — no prior known-good kernel tested

System:
Lenovo ThinkPad X390 Yoga
Thunderbolt controller path: 00:1c.4 → 07:00.0 → 08:02.0 → 2f:00.0
lspci -s 2f:00.0: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan
Ridge 4C 2018], vendor 0x8086, device 0x15c1

The error usually show like this:
usb 4-1: new SuperSpeed USB device number N using xhci_hcd
usb 4-1: New USB device found, idVendor=0781, idProduct=55a9
scsi host0: uas
scsi 0:0:0:0: Direct-Access      USB      SanDisk 3.2Gen1
sd 0:0:0:0: [sda] 120164352 512-byte logical blocks
usb 4-1: USB disconnect, device number N
sd 0:0:0:0: [sda] tag#0 uas_zap_pending 0 uas-tag 1 inflight: CMD
sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT

I have tried udev rules, usb quirks and nothing seems to fix the issue.
System freezes do not occur at all.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2026-09-20 15:06 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 10:25 [Bug 216728] New: Thunderbolt USB Controller died after resume on Intel CometLake platform bugzilla-daemon
2022-11-22 10:27 ` [Bug 216728] " bugzilla-daemon
2022-11-22 10:29 ` bugzilla-daemon
2022-11-24  9:19 ` bugzilla-daemon
2022-11-25  1:42 ` bugzilla-daemon
2022-11-25  6:34 ` bugzilla-daemon
2022-11-25  7:58 ` bugzilla-daemon
2022-11-28 10:47 ` bugzilla-daemon
2022-11-28 12:41 ` bugzilla-daemon
2022-11-28 12:42 ` bugzilla-daemon
2022-11-28 12:54 ` bugzilla-daemon
2022-11-29  3:26 ` bugzilla-daemon
2022-11-29 11:31 ` bugzilla-daemon
2022-11-29 11:33 ` bugzilla-daemon
2022-11-30  2:50 ` bugzilla-daemon
2022-11-30  2:52 ` bugzilla-daemon
2022-11-30  8:06 ` bugzilla-daemon
2022-11-30 13:17 ` bugzilla-daemon
2022-12-14  8:25 ` bugzilla-daemon
2022-12-15 11:52 ` bugzilla-daemon
2022-12-16  7:51 ` bugzilla-daemon
2022-12-16  7:55 ` bugzilla-daemon
2023-01-13 14:33 ` bugzilla-daemon
2023-02-01  7:20 ` bugzilla-daemon
2023-02-01  7:21 ` bugzilla-daemon
2023-02-08  4:29 ` bugzilla-daemon
2023-02-08 13:54 ` bugzilla-daemon
2023-03-06 12:03 ` bugzilla-daemon
2023-05-02 10:59 ` bugzilla-daemon
2023-05-02 11:00 ` bugzilla-daemon
2023-05-02 12:31 ` bugzilla-daemon
2023-05-15  1:57 ` bugzilla-daemon
2023-07-02 18:49 ` bugzilla-daemon
2023-07-02 18:50 ` bugzilla-daemon
2023-07-05 23:52 ` bugzilla-daemon
2023-08-21 12:34 ` bugzilla-daemon
2023-08-25 11:13 ` bugzilla-daemon
2023-08-30  0:41 ` bugzilla-daemon
2023-09-14 12:30 ` bugzilla-daemon
2023-09-14 15:46 ` bugzilla-daemon
2023-09-14 22:32 ` bugzilla-daemon
2023-09-14 22:39 ` bugzilla-daemon
2023-09-15 10:31 ` bugzilla-daemon
2023-09-15 10:32 ` bugzilla-daemon
2023-09-15 23:12 ` bugzilla-daemon
2024-02-12 20:29 ` bugzilla-daemon
2024-02-12 20:30 ` bugzilla-daemon
2024-02-13  7:08 ` bugzilla-daemon
2026-04-24 19:47 ` bugzilla-daemon
2026-09-20 15:06 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-216728-208809-QFGirDJmzU@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox