https://bugs.freedesktop.org/show_bug.cgi?id=106303
Bug ID: 106303 Summary: amdgpu on RX 560: memory and core clocks not lowered on idle Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: bugs.freedesktop.org@pm.port0.org
Created attachment 139206 --> https://bugs.freedesktop.org/attachment.cgi?id=139206&action=edit amdgpu_pm_info with 4.15 kernel
There is a problem with amdgpu power management. With kernels 4.15.X MCLK is always stays at max value. With kernels 4.16.X MCLK/SCLK both stays at max.
At idle desktop GPU draws about 4W more, according to /sys/kernel/debug/dri/0/amdgpu_pm_info
Kernels from Ubuntu PPA http://kernel.ubuntu.com/~kernel-ppa/mainline/
DRM/Mesa libs from Oibaf PPA https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #1 from Mike bugs.freedesktop.org@pm.port0.org --- Created attachment 139207 --> https://bugs.freedesktop.org/attachment.cgi?id=139207&action=edit amdgpu_pm_info with 4.16 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #2 from Mike bugs.freedesktop.org@pm.port0.org --- Created attachment 139208 --> https://bugs.freedesktop.org/attachment.cgi?id=139208&action=edit syslog (non0-kernel stuff removed)
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #3 from Mike bugs.freedesktop.org@pm.port0.org --- Also noted, that /sys/class/drm/card0/device/pp_num_states is limited to: states: 2 0 boot 1 performance
And power_dpm_state is always 'performance' regarless of values echoed to power_dpm_force_performance_level (tried 'low', 'auto', 'balanced' and 'boot').
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #4 from Alex Deucher alexdeucher@gmail.com --- Can you bisect? Are you using multiple monitors?
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #5 from Mike bugs.freedesktop.org@pm.port0.org ---
Can you bisect?
No, I'm using pre-compiled kernels. However, it's clearly happens in-between 4.15.8 and 4.16.{0 .. 2}. Reproduces stably.
Are you using multiple monitors?
No, single monitor via DisplayPort (2560x1440x144).
PS. I'm also use amdgpu.dc=1
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #6 from Julian jsbansen@gmail.com --- Can confirm. I'm using a Rx 560 on kernel 4.16 and my clock rate is stuck on 1230MHz permanently.
I'm also using a single 2560x1440x144 monitor
This is directly related to DC. If I run with amdgpu.dc=0 the issue disappears. If I run with amdgpu.dc=1 it shows up. I can't say if it also happened on 4.15 or earlier.
I did notice that dmesg shows about a dozen powerplay errors:
[ 94.582083] amdgpu: [powerplay] failed to send message 146 ret is 255 [ 94.582091] amdgpu: [powerplay] failed to send pre message 147 ret is 255 [ 95.895976] amdgpu: [powerplay] failed to send message 145 ret is 255
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #7 from Mike bugs.freedesktop.org@pm.port0.org --- Power usage partially improved with kernel 4.17.2 Both MCLK and SCLK now lowered to full idle - when monitor is turned OFF.
Also MCLK seems to go idle (300MHz) periodically under low load (2D and browsing). However, SCLK is still run at top values when monitor is ON, regardless of GPU load (it is about 1-2% according to radeontop utility).
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #8 from Julian jsbansen@gmail.com --- This appears to be fixed for me on 4.18.16. My 570's shader clock now properly goes down to 300MHz on idle, like it does using amdgpu.dc=0.
https://bugs.freedesktop.org/show_bug.cgi?id=106303
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #9 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/367.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org