From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung! Date: Sat, 13 Apr 2019 13:27:53 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0280736073==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 194A7892D8 for ; Sat, 13 Apr 2019 13:27:54 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0280736073== Content-Type: multipart/alternative; boundary="15551620740.449eC.10280" Content-Transfer-Encoding: 7bit --15551620740.449eC.10280 Date: Sat, 13 Apr 2019 13:27:54 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D102322 --- Comment #81 from Jaap Buurman --- (In reply to Alex Deucher from comment #14) > (In reply to dwagner from comment #13) > >=20 > > Much lower shader clocks are used only if I lower the refresh rate of t= he > > screen. Is there a reason why the shader clocks should stay high even i= n the > > absence of 3d/compute load? > >=20 >=20 > 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=3D109955), everybody having t= he 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 graspi= ng at straws here, but I have had this problem for as long as I have this Vega= 64 (bought at launch), while it is 100% stable under Windows 10 in the same se= tup. --=20 You are receiving this mail because: You are the assignee for the bug.= --15551620740.449eC.10280 Date: Sat, 13 Apr 2019 13:27:54 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 81 on bug 10232= 2 from Jaap Buurman 
(In reply to Alex Deucher from comment #14)
> (In reply to dwagner from comment #13)
> >=20
> > Much lower shader clocks are used only if I lower the refresh rat=
e of the
> > screen. Is there a reason why the shader clocks should stay high =
even in the
> > absence of 3d/compute load?
> >=20
>=20
> Certain display requirements can cause the engine clock to be kept hig=
her as
> well.

In this bug report and another similar one
(https://bugs.freedesktop.org/show_bug.=
cgi?id=3D109955), 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 graspi=
ng
at straws here, but I have had this problem for as long as I have this Vega=
64
(bought at launch), while it is 100% stable under Windows 10 in the same se=
tup.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551620740.449eC.10280-- --===============0280736073== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0280736073==--