[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=102322

--- Comment #81 from Jaap Buurman <jaapbuurman at gmail.com> ---
(In reply to Alex Deucher from comment #14)
> (In reply to dwagner from comment #13)
> > 
> > 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
(https://bugs.freedesktop.org/show_bug.cgi?id=109955), 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20190413/359be576/attachment.html>