From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220284] New: USB4 / Thunderbolt not working after boot until thunderbolt module is reloaded
Date: Fri, 27 Jun 2025 17:29:56 +0000 [thread overview]
Message-ID: <bug-220284-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220284
Bug ID: 220284
Summary: USB4 / Thunderbolt not working after boot until
thunderbolt module is reloaded
Product: Drivers
Version: 2.5
Kernel Version: 6.15.3
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: kim.lindberger@gmail.com
Regression: Yes
Laptop: Lenovo ThinkPad T14s Gen 4, model 21F8CTO1WW (AMD)
When upgrading from 6.15.2 to 6.15.3 my ThinkPad Thunderbolt 4 Dock stopped
working, giving basically no signs of life even when unplugged and replugged.
It doesn't start working again until the thunderbolt module is unloaded and
reloaded while the dock is still connected. If I unload and reload while the
dock is disconnected, nothing happens.
When booting, I can also see
thunderbolt 0000:c5:00.6: probe with driver thunderbolt failed with error -110
in the log, which wasn't printed with prior kernels.
I don't boot with the dock connected.
The issue persist with 6.15.4.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-06-27 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 17:29 bugzilla-daemon [this message]
2025-06-28 12:53 ` [Bug 220284] New: USB4 / Thunderbolt not working after boot until thunderbolt module is reloaded Alyssa Ross
2025-06-28 12:53 ` [Bug 220284] " bugzilla-daemon
2025-08-13 6:08 ` bugzilla-daemon
2025-08-14 4:44 ` bugzilla-daemon
2025-11-02 14:48 ` bugzilla-daemon
2025-11-08 11:57 ` bugzilla-daemon
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-220284-208809@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