https://bugzilla.kernel.org/show_bug.cgi?id=214071
Bug ID: 214071 Summary: amdgpu idle power draw to high at +75Hz Product: Drivers Version: 2.5 Kernel Version: 5.13.10 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: pb.g@gmx.de Regression: No
For best viewing pleasure I usually set my monitor to 144Hz and native 1080p.
At that refresh rate my RX6900XT draws about 35 Watts in idle situations Memory clock stays at 1000Hz.
I have to lower the monitors refresh rate to 75Hz, then the card draws only 8 Watts in idle and memory clock goes significantly down to 96MHz.
Using 100 or 120 Hz does not help.
Situation in windows is different. The same hardware setup works in Windows10 at 1080p@144 with idle power draw of just 8 Watts.
So my guess is this is a driver issue and not a hardware issue.
https://bugzilla.kernel.org/show_bug.cgi?id=214071
Paul Größel (pb.g@gmx.de) changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|amdgpu idle power draw to |amdgpu idle power draw too |high at +75Hz |high at +75Hz
https://bugzilla.kernel.org/show_bug.cgi?id=214071
--- Comment #1 from Paul Größel (pb.g@gmx.de) --- Hardware setup: Mainboard: MSI MPG B550I GAMING EDGE WIFI CPU: Ryzen 5950X GPU: Radeon RX 6900XT
Kernel 5.13.10 mesa 21.1.4 X11
https://bugzilla.kernel.org/show_bug.cgi?id=214071
kasimir (info@lox.enterprises) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |info@lox.enterprises
--- Comment #2 from kasimir (info@lox.enterprises) --- Anything happening with this bug? I noticed the same behavior, but like to add it's fine for me at 100Hz (using ~7W) only at 120Hz it fires up (~35W).
I have an AMD RX 6900XT with kernel 5.17.1 and Mesa 22.0.0 (on GNOME/Xorg, Arch Linux).
https://bugzilla.kernel.org/show_bug.cgi?id=214071
Alex Deucher (alexdeucher@gmail.com) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexdeucher@gmail.com
--- Comment #3 from Alex Deucher (alexdeucher@gmail.com) --- The driver can only change memory clocks during display blanking periods to avoid display glitches. If the blanking period is too short, the driver can't change the memory clock so it keeps it clocked high. You could try adjusting the modelines for the problematic modes to extend the blanking periods and see if that helps.
dri-devel@lists.freedesktop.org