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: Sun, 10 Feb 2019 01:01:52 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2060188586==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C81E36E0A9 for ; Sun, 10 Feb 2019 01:01:52 +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 --===============2060188586== Content-Type: multipart/alternative; boundary="15497605120.Fde728A.25888" Content-Transfer-Encoding: 7bit --15497605120.Fde728A.25888 Date: Sun, 10 Feb 2019 01:01:52 +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 #12 from Tom Seewald --- (In reply to Alex Deucher from comment #11) > The reset was actually successful. The problem is, userspace components > need to be aware of the reset and recreate their contexts. As a workarou= nd, > you can kill the problematic app or restart X. Hmm, but then why will the machine not restart unless I use sysrq keys? I w= ould think a userspace issue wouldn't cause hung kernel tasks like that. I'm also curious regarding why this program is causing the GPU to reset to begin with, I have not seen others reporting issues on other platforms with this program. Is this ring gfx timeout purely a problem with userspace? e.g. [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D32203, emitted seq=3D32205 --=20 You are receiving this mail because: You are the assignee for the bug.= --15497605120.Fde728A.25888 Date: Sun, 10 Feb 2019 01:01:52 +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 # 12 on bug 10885= 4 from Tom Seewald 
(In reply to Alex Deucher from comment #11)
> The reset was actually successful.  The problem =
is, userspace components
> need to be aware of the reset and recreate their contexts.  As a worka=
round,
> you can kill the problematic app or restart X.

Hmm, but then why will the machine not restart unless I use sysrq keys? I w=
ould
think a userspace issue wouldn't cause hung kernel tasks like that.

I'm also curious regarding why this program is causing the GPU to reset to
begin with, I have not seen others reporting issues on other platforms with
this program.

Is this ring gfx timeout purely a problem with userspace?

e.g.
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled
seq=3D32203, emitted seq=3D32205

You are receiving this mail because:
  • You are the assignee for the bug.
= --15497605120.Fde728A.25888-- --===============2060188586== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============2060188586==--