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: Tue, 09 Jul 2019 07:38:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1080029124==" 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 4A02F6E061 for ; Tue, 9 Jul 2019 07:38:26 +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 --===============1080029124== Content-Type: multipart/alternative; boundary="15626579063.B7921ae9.30285" Content-Transfer-Encoding: 7bit --15626579063.B7921ae9.30285 Date: Tue, 9 Jul 2019 07:38:26 +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 #84 from Wilko Bartels --- (In reply to Wilko Bartels from comment #83) > (In reply to Jaap Buurman from comment #81) > > issue seems to be using a setup that requires higher engine clocks in i= dle > > 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 h= ave > > this Vega64 (bought at launch), while it is 100% stable under Windows 1= 0 in > > the same setup. >=20 > This might be true. I was running i3 with xrandr set to 144hz when the > freeze scenario began (somewhat last mont, did not "game" much before). T= han > switched to icewm to test and issue was gone. Later when i configured ice= wm > to also have proper xrandr setting issue comes back. I didnt know that co= uld > be related. Will test this tonight. nevermind. it crashed on 60hz as well (once) yesterday --=20 You are receiving this mail because: You are the assignee for the bug.= --15626579063.B7921ae9.30285 Date: Tue, 9 Jul 2019 07:38:26 +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 # 84 on bug 10232= 2 from = Wilko Bartels 
(In reply to Wilko Bartels from comment #83)
> (In reply to Jaap Buurman from comment #81)
> > issue seems to be using a setup that requires higher engine clock=
s in idle
> > AFAIK. Either high refresh displays, or in my case, multiple moni=
tors. 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 Win=
dows 10 in
> > the same setup.
>=20
> This might be true. I was running i3 with xrandr set to 144hz when the
> freeze scenario began (somewhat last mont, did not "game" mu=
ch before). Than
> switched to icewm to test and issue was gone. Later when i configured =
icewm
> to also have proper xrandr setting issue comes back. I didnt know that=
 could
> be related. Will test this tonight.

nevermind. it crashed on 60hz as well (once) yesterday

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