From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218525] Thunderbolt eGPU bad performance
Date: Wed, 06 Mar 2024 02:18:57 +0000 [thread overview]
Message-ID: <bug-218525-208809-hytt4F5Lfg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218525-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218525
Benjamin (benjamin.sabatini@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |benjamin.sabatini@gmail.com
--- Comment #15 from Benjamin (benjamin.sabatini@gmail.com) ---
(In reply to Mika Westerberg from comment #13)
> Okay with this you have ASPM disabled:
>
> LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
> ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s (downgraded), Width x4 (downgraded)
> TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
>
> However, the link speed is now at gen 1 but I guess that gets adjusted then
> as you mentioned. I suggest to check that when you play some affected game
> that it actually runs at the 8GT/s x 4.
>
> One more thing comes to mind but you probably checked it already. The game
> may not be using the eGPU and instead it is running on the internal one.
> With the Unigine benchmark it clearly used the eGPU.
Hello. I'm just confirming the issue over TB4 on a Lenovo Z13 laptop and RX
7600 XT in an eGPU setup using the same kernel parameters as workarounds
(amd_iommu=off instead). It never pulls more than ~50 watts and maybe ~2000MHz
on the GPU and ~400 MHz on the VRAM.
--
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:[~2024-03-06 2:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 10:14 [Bug 218525] New: Thunderbolt eGPU bad performance bugzilla-daemon
2024-02-24 11:45 ` [Bug 218525] " bugzilla-daemon
2024-02-26 6:35 ` bugzilla-daemon
2024-02-29 1:49 ` bugzilla-daemon
2024-02-29 1:50 ` bugzilla-daemon
2024-02-29 1:50 ` bugzilla-daemon
2024-02-29 1:55 ` bugzilla-daemon
2024-02-29 1:55 ` bugzilla-daemon
2024-02-29 9:07 ` bugzilla-daemon
2024-03-01 6:42 ` bugzilla-daemon
2024-03-01 8:59 ` bugzilla-daemon
2024-03-01 9:00 ` bugzilla-daemon
2024-03-01 9:00 ` bugzilla-daemon
2024-03-01 9:39 ` bugzilla-daemon
2024-03-01 9:46 ` bugzilla-daemon
2024-03-06 2:18 ` bugzilla-daemon [this message]
2024-03-08 8:17 ` bugzilla-daemon
2024-09-08 12:53 ` bugzilla-daemon
2025-01-06 22:12 ` 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-218525-208809-hytt4F5Lfg@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;
as well as URLs for NNTP newsgroup(s).