From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 108854] [polaris11] - GPU Hang - ring gfx timeout Date: Thu, 21 Feb 2019 19:21:57 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1706596077==" 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 1265B892F6 for ; Thu, 21 Feb 2019 19:21:57 +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 --===============1706596077== Content-Type: multipart/alternative; boundary="15507769160.63049aB.13111" Content-Transfer-Encoding: 7bit --15507769160.63049aB.13111 Date: Thu, 21 Feb 2019 19:21:56 +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=3D108854 --- Comment #14 from Tom Seewald --- (In reply to Tom St Denis from comment #13) > The wave dump seems to be empty... Is that the complete output? Was there > anything printed to stderr (like there are no waves)? Yes it says "no active waves!" - so it makes sense that is empty. Is there something else you'd like me to try?=20 Currently I'm running "umr -i 1 -O verbose,halt_waves -wa" immediately afte= r I see the "ring gfx timeout" in dmesg. I also just rebuilt UMR so I should b= e up to date. Some potentially good news though, after upgrading from mesa 18.3.1 to 18.3= .3, I have not been able to reproduce the issue. On mesa 18.3.1 and earlier I c= an reproduce it in under 20 seconds (I did so today on the latest amd-staging-drm-next), and I have tested mesa 18.3.3 for about an hour now. But I believe this is still something to look into as user space should probably not be able to hang the entire system, even if the user is running= an older version of Mesa. --=20 You are receiving this mail because: You are the assignee for the bug.= --15507769160.63049aB.13111 Date: Thu, 21 Feb 2019 19:21:56 +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 # 14 on bug 10885= 4 from Tom Seewald 
(In reply to Tom St Denis from comment #13)
> The wave dump seems to be empty... Is that the c=
omplete output?  Was there
> anything printed to stderr (like there are no waves)?

Yes it says "no active waves!" - so it makes sense that is empty.=
  Is there
something else you'd like me to try?=20

Currently I'm running "umr -i 1 -O verbose,halt_waves -wa" immedi=
ately after I
see the "ring gfx timeout" in dmesg.  I also just rebuilt UMR so =
I should be up
to date.

Some potentially good news though, after upgrading from mesa 18.3.1 to 18.3=
.3,
I have not been able to reproduce the issue. On mesa 18.3.1 and earlier I c=
an
reproduce it in under 20 seconds (I did so today on the latest
amd-staging-drm-next), and I have tested mesa 18.3.3 for about an hour now.

But I believe this is still something to look into as user space should
probably not be able to hang the entire system, even if the user is running=
 an
older version of Mesa.

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