| Bug ID | 106177 |
|---|---|
| Summary | overclocking doesn't work with 4.17-rc1 |
| Product | DRI |
| Version | DRI git |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | haagch@frickel.club |
RX 480. I noticed a while ago that overclocking didn't work on drm-next-4.17-wip/drm-next-4.18-wip, but now it's gotten into mainline. With linux 4.16.3 overclockling works fine. With 4.17-rc1 the setting doesn't "stick" and the clocks aren't i= ncreased: root@c-pc ~ # cat /sys/class/drm/card0/device/pp_sclk_od 0 root@c-pc ~ # cat /sys/class/drm/card0/device/pp_dpm_sclk 0: 300Mhz * 1: 608Mhz 2: 910Mhz 3: 1077Mhz 4: 1145Mhz 5: 1191Mhz 6: 1236Mhz 7: 1288Mhz root@c-pc ~ # echo 2 > /sys/class/drm/card0/device/pp_sclk_od root@c-pc ~ # cat /sys/class/drm/card0/device/pp_sclk_od 0 root@c-pc ~ # cat /sys/class/drm/card0/device/pp_dpm_sclk 0: 300Mhz * 1: 608Mhz 2: 910Mhz 3: 1077Mhz 4: 1145Mhz 5: 1191Mhz 6: 1236Mhz 7: 1288Mhz
| What | Removed | Added |
|---|---|---|
| CC | grmat@sub.red |
I have the same issue on 4.16.6 and 4.17-rc2 and CIK hardware = (Hawaii/R9 290X)
I just tried 4.16.7 and overclocking still works on the 4.16 v= ersion. And I think on 4.17rc3 it still doesn't work. Do you mean on 4.16.6 overclocking does not work for you? Then it's probably not the same as my issue.
At least I had the same behaviour, value not "sticky"= ; and no impact on actual clock. I noticed it when I tested 4.17-rc2, actually wanted to test the "watt= man" functionality. Then noticed, it doesn't work on the 4.16.6 either. Will hav= e to test older kernels, maybe this weekend.
I'm on a RX 560. I can confirm that with 4.17, behavior has quite changed a lot. I don't thi= nk it's buggy for Polaris, but not documented correctly. To make values "stick" in pp_sclk_od, you have to boot with the p= arameter amdgpu.ppfeaturemask=3D0xffffffff. Applying values higher than 1 in pp_sclk_od don't get reported back correct= ly, cat pp_sclk_od always returns 1. However, entering values higher than 1 have an effect despite of this, as t= hey allow using of higher clocks in pp_od_clk_voltage. And unlike with 4.16, higher values than 0 in pp_sclk_od don't automatically lead to higher clocks. Additionally it is also required to change the pstat= es in pp_od_clk_voltage (again unlocked with amdgpu.ppfeaturemask=3D0xffffffff= ).
Please use debugfs (e.g., /sys/kernel/debug/dri/0/amdgpu_pm_in= fo) to check the current clocks.
I have not tried amdgpu.ppfeaturemask=3D0xffffffff etc. yet.
If a behavior change like that is intended, there should be some easily
accessible documentation about it somewhere.
1288 MHz (SCLK) is the factory overclocked default max clock, so debugfs ag=
rees
that pp_sclk_od on its own does nothing with 4.17rc4.
root@c-pc ~ # echo high >
/sys/class/drm/card0/device/power_dpm_force_performance_level
root@c-pc ~ # echo 5 > /sys/class/drm/card0/device/pp_sclk_od
root@c-pc ~ # cat /sys/kernel/debug/dri/0/amdgpu_pm_info
Clock Gating Flags Mask: 0x37bcf
Graphics Medium Grain Clock Gating: On
Graphics Medium Grain memory Light Sleep: On
Graphics Coarse Grain Clock Gating: On
Graphics Coarse Grain memory Light Sleep: On
Graphics Coarse Grain Tree Shader Clock Gating: Off
Graphics Coarse Grain Tree Shader Light Sleep: Off
Graphics Command Processor Light Sleep: On
Graphics Run List Controller Light Sleep: On
Graphics 3D Coarse Grain Clock Gating: Off
Graphics 3D Coarse Grain memory Light Sleep: Off
Memory Controller Light Sleep: On
Memory Controller Medium Grain Clock Gating: On
System Direct Memory Access Light Sleep: Off
System Direct Memory Access Medium Grain Clock Gating: On
Bus Interface Medium Grain Clock Gating: Off
Bus Interface Light Sleep: On
Unified Video Decoder Medium Grain Clock Gating: On
Video Compression Engine Medium Grain Clock Gating: On
Host Data Path Light Sleep: Off
Host Data Path Medium Grain Clock Gating: On
Digital Right Management Medium Grain Clock Gating: Off
Digital Right Management Light Sleep: Off
Rom Medium Grain Clock Gating: On
Data Fabric Medium Grain Clock Gating: Off
GFX Clocks and Power:
2000 MHz (MCLK)
1288 MHz (SCLK)
300 MHz (PSTATE_SCLK)
601 MHz (PSTATE_MCLK)
1093 mV (VDDGFX)
19.166 W (VDDC)
15.19 W (VDDCI)
40.200 W (max GPU)
40.185 W (average GPU)
GPU Temperature: 43 C
GPU Load: 0 %
UVD: Disabled
VCE: Disabled
I can confirm this behaviour with kernel 4.16 and point releas= e 16 and 18 it works as I would expect, with kernel 4.17, 4.18.14 and 4.19 from drm fixes = git it doesn't work. Setting feature mask have no effect.=20 Polaris Rx 460
same effect as Christoph Haag mentions echoing pp_dpm_mclk and= pp_mclk_od reports nothing changed.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | NOTABUG |
| Status | NEW | RESOLVED |
this is not a bug. tempel julian is right. There is also the a= rchwiki which explain this also. Behaviour has changed but it's not a bug.
check here=20 https:= //wiki.archlinux.org/index.php/AMDGPU#Overclocking and it's documented on the kernel source
(In reply to alvarex from comment #10) > check here=20 > h= ttps://wiki.archlinux.org/index.php/AMDGPU#Overclocking >=20 > and it's documented on the kernel source The arch wiki has some errors in it as well. Here's the kernel documentati= on: https://dri.freedesktop.org/docs/drm/gpu/am= dgpu.html#gpu-power-thermal-controls-and-monitoring