From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 220906] Regression: 4K display output fails on ThinkPad Thunderbolt 4 Dock with AMD GPU (Worked in 6.17.1, broken in 6.17.11)
Date: Sat, 27 Dec 2025 20:14:29 +0000 [thread overview]
Message-ID: <bug-220906-2300-EErLOuylPj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220906-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220906
--- Comment #7 from Andrei (danandrei@gmail.com) ---
I initially thought this was just an AMD driver bug, but after digging through
the logs across a few more versions, I think I’ve found a better lead.
In 6.17.6, where the regression started for the first time, I'm seeing these
bridge resource failures pop up for the first time:
pci 0000:02:00.0: bridge window [io size 0x1000]: can't assign; no space
pci 0000:02:00.0: bridge window [io size 0x1000]: failed to assign
Bridge 02:00.0 is the gateway for the USB4/Thunderbolt 4 controller on this
machine. In version 6.17.5, the kernel assigns it just fine and my 4K output
works perfectly. Starting with 6.17.6, that assignment fails, which lines up
exactly with when the display stops working.
Interestingly, the ath12k driver also starts throwing an "invalid ACPI DSM TAS
config size" error in this same version. It feels like 6.17.6 changed something
fundamental about how ACPI or PCI resource arbitration is handled, and now it's
just choking out the I/O space that the Thunderbolt subsystem needs to
function.
--
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 prev parent reply other threads:[~2025-12-27 20:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 21:41 [Bug 220906] New: Regression: 4K display output fails on ThinkPad Thunderbolt 4 Dock with AMD GPU (Worked in 6.17.1, broken in 6.17.11) bugzilla-daemon
2025-12-24 21:43 ` [Bug 220906] " bugzilla-daemon
2025-12-24 21:43 ` bugzilla-daemon
2025-12-26 7:39 ` bugzilla-daemon
2025-12-27 19:28 ` bugzilla-daemon
2025-12-27 19:29 ` bugzilla-daemon
2025-12-27 19:29 ` bugzilla-daemon
2025-12-27 19:30 ` bugzilla-daemon
2025-12-27 19:53 ` bugzilla-daemon
2025-12-27 20:14 ` bugzilla-daemon [this message]
2025-12-27 20:16 ` bugzilla-daemon
2025-12-28 8:17 ` bugzilla-daemon
2025-12-28 20:41 ` 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-220906-2300-EErLOuylPj@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.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.