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: Fri, 24 Apr 2026 19:47:20 +0000 [thread overview]
Message-ID: <bug-216728-208809-oFggVGt8Hr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216728-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216728
--- Comment #48 from STRSHR (strasharo2000@yahoo.com) ---
Still reproducible on kernel 6.19.13 (Fedora 43), ThinkPad P1 Gen 3, Intel
Comet Lake-H.
Hardware: Intel JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018]
(8086:15ec, rev 06) at 0000:2c:00.0
Trigger: Hotplugging a USB-C Ethernet adapter (Realtek r8152 chipset) into a
Thunderbolt 3 port. No dock involved â a plain USB-C adapter is sufficient to
reproduce.
Sequence: The adapter enumerates fine (~37s after boot). ~52 seconds later the
runtime PM puts the xHCI controller to D3. On the next access the resume fails:
xhci_hcd 0000:2c:00.0: Controller not ready at resume -19
xhci_hcd 0000:2c:00.0: PCI post-resume error -19!
xhci_hcd 0000:2c:00.0: HC died; cleaning up
xhci_hcd 0000:2c:00.0: xHCI host controller not responding, assume dead
xhci_hcd 0000:2c:00.0: HC died; cleaning up
xhci_hcd 0000:2c:00.0: Timeout while waiting for configure endpoint command
The system continues running for several minutes with the dead controller, then
freezes hard (requires power button hold).
Workaround: Keeping the controller out of D3 prevents the crash entirely:
echo on > /sys/bus/pci/devices/0000:2c:00.0/power/control
Persisted via udev rule matching vendor/device IDs:
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x8086",
ATTR{device}=="0x15ec", ATTR{power/control}="on"
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-04-24 19:47 UTC|newest]
Thread overview: 49+ 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 [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-oFggVGt8Hr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.