<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!" href="https://bugs.freedesktop.org/show_bug.cgi?id=102322#c81">Comment # 81</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!" href="https://bugs.freedesktop.org/show_bug.cgi?id=102322">bug 102322</a> from <a class="email" href="mailto:jaapbuurman@gmail.com" title="Jaap Buurman <jaapbuurman@gmail.com>"> Jaap Buurman</a> <pre>(In reply to Alex Deucher from <a href="show_bug.cgi?id=102322#c14">comment #14</a>) > (In reply to dwagner from <a href="show_bug.cgi?id=102322#c13">comment #13</a>) > > > > Much lower shader clocks are used only if I lower the refresh rate of the > > screen. Is there a reason why the shader clocks should stay high even in the > > absence of 3d/compute load? > > > > Certain display requirements can cause the engine clock to be kept higher as > well. In this bug report and another similar one (<a class="bz_bug_link bz_status_NEW " title="NEW - amdgpu [RX Vega 64] system freeze while gaming" href="show_bug.cgi?id=109955">https://bugs.freedesktop.org/show_bug.cgi?id=109955</a>), everybody having the issue seems to be using a setup that requires higher engine clocks in idle AFAIK. Either high refresh displays, or in my case, multiple monitors. Could this be part of the issue that seems to trigger this bug? I might be grasping at straws here, but I have had this problem for as long as I have this Vega64 (bought at launch), while it is 100% stable under Windows 10 in the same setup.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>