From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221293] New: Thunderbolt: "failed to calculate available bandwidth" causes DisplayPort tunnel drop with Apple Studio Display
Date: Sat, 28 Mar 2026 22:26:40 +0000 [thread overview]
Message-ID: <bug-221293-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221293
Bug ID: 221293
Summary: Thunderbolt: "failed to calculate available bandwidth"
causes DisplayPort tunnel drop with Apple Studio
Display
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: aylin.ahmed@jetbot.co.uk
Regression: No
Created attachment 309779
--> https://bugzilla.kernel.org/attachment.cgi?id=309779&action=edit
dmesg thunderbolt log and hardware details
Apple Studio Display connected via Thunderbolt to ThinkPad X1 Carbon
intermittently loses DisplayPort tunnel. The kernel logs:
thunderbolt 0000:00:0d.3: 0:12 <-> 1:20 (USB3): failed to calculate available
bandwidth
followed by "failed to reach state TB_PORT_UP" and device disconnect.
USB3 hub (05ac:8014) and DP contend for bandwidth. Manually unbinding the USB3
hub restores DP, confirming contention. Suspend/resume recovers correctly but
DPMS wake does not.
Hardware: ThinkPad X1 Carbon, Intel Gen12 TB controller, kernel
6.8.0-106-generic, Ubuntu 24.x Wayland.
Full dmesg and hardware details attached.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2026-03-28 22:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-221293-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