From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219748] Pluggable UD-4VPD dock appears to continually reset with AMD AI 365
Date: Tue, 04 Mar 2025 23:41:55 +0000 [thread overview]
Message-ID: <bug-219748-208809-WWH6cSxteL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219748-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219748
Sean (sean@bioslevel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sean@bioslevel.com
--- Comment #18 from Sean (sean@bioslevel.com) ---
Created attachment 307767
--> https://bugzilla.kernel.org/attachment.cgi?id=307767&action=edit
dmesg after Scan downstream retimers after the router patch
While this topic is related to a Plugable dock, the Thunderbolt implementation
is having some issues for AMD GPUs where display EDIDs can't be read
(https://gitlab.freedesktop.org/drm/amd/-/issues/3050). This latest patch
appears to have helped that issue, as my TB3 Lenovo dock on a Framework 16
with an AMD 7840HS CPU is now able to use its display outputs at the correct
resolutions. I'll be testing with addition TB docks I have access to in the
near future as well.
--
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-03-04 23:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 20:58 [Bug 219748] New: Pluggable UD-4VPD dock appears to continually reset with AMD AI 365 bugzilla-daemon
2025-02-03 20:58 ` [Bug 219748] " bugzilla-daemon
2025-02-04 6:49 ` bugzilla-daemon
2025-02-05 23:14 ` bugzilla-daemon
2025-02-05 23:15 ` bugzilla-daemon
2025-02-05 23:17 ` bugzilla-daemon
2025-02-06 15:51 ` bugzilla-daemon
2025-02-09 19:50 ` bugzilla-daemon
2025-02-10 7:30 ` bugzilla-daemon
2025-02-14 19:46 ` bugzilla-daemon
2025-02-14 19:47 ` bugzilla-daemon
2025-02-14 19:50 ` bugzilla-daemon
2025-02-14 21:31 ` bugzilla-daemon
2025-02-24 6:44 ` bugzilla-daemon
2025-02-24 7:58 ` bugzilla-daemon
2025-03-03 16:06 ` bugzilla-daemon
2025-03-04 8:44 ` bugzilla-daemon
2025-03-04 8:46 ` bugzilla-daemon
2025-03-04 23:41 ` bugzilla-daemon [this message]
2025-03-05 1:30 ` bugzilla-daemon
2025-03-05 9:26 ` bugzilla-daemon
2025-03-05 9:31 ` bugzilla-daemon
2025-03-05 11:52 ` bugzilla-daemon
2025-03-05 12:40 ` bugzilla-daemon
2025-03-05 13:11 ` bugzilla-daemon
2025-03-05 14:34 ` bugzilla-daemon
2025-03-05 23:33 ` bugzilla-daemon
2025-03-05 23:35 ` bugzilla-daemon
2025-03-06 3:53 ` bugzilla-daemon
2025-03-06 7:16 ` bugzilla-daemon
2025-03-06 17:24 ` bugzilla-daemon
2025-03-07 10:39 ` bugzilla-daemon
2025-03-07 20:38 ` bugzilla-daemon
2025-03-07 21:02 ` bugzilla-daemon
2025-03-12 9:33 ` bugzilla-daemon
2025-04-03 2:55 ` 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-219748-208809-WWH6cSxteL@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.