<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - amdgpu [RX Vega 64] system freeze while gaming" href="https://bugs.freedesktop.org/show_bug.cgi?id=109955#c129">Comment # 129</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - amdgpu [RX Vega 64] system freeze while gaming" href="https://bugs.freedesktop.org/show_bug.cgi?id=109955">bug 109955</a> from <a class="email" href="mailto:me@jasondaigo.de" title="Wilko Bartels <me@jasondaigo.de>"> Wilko Bartels</a> <pre>(In reply to haro41 from <a href="show_bug.cgi?id=109955#c122">comment #122</a>) > In my experience, this issue is related to mclk switching and it affects the > lowest mclk level only. > > So you guy's can save a lot of power, if you, insteed of switching to > highest gfxlevel or to disable vsync, just disable the lowest mclk level by: > > echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level > echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk > > If you are building your kernel locally, look in this thread for a driver > code modification that works, without disabling the lowest mclk level (saves > a few watt on idle). do you have any suggestion to automate this? so far i can strictly run these commands after su. not even sudo works with scripts running these commands. or systemd files.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>