From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 98874] amdgpu: [drm:amdgpu_job_timedout] *ERROR* ring gfx timeout, [drm] IP block:5 is hang Date: Sun, 20 Aug 2017 22:55:31 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1099700431==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id ABB4A6E04F for ; Sun, 20 Aug 2017 22:55:31 +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 --===============1099700431== Content-Type: multipart/alternative; boundary="15032697310.aCC29A.998"; charset="UTF-8" --15032697310.aCC29A.998 Date: Sun, 20 Aug 2017 22:55:31 +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=3D98874 --- Comment #13 from dwagner --- Notice that my bug report https://bugs.freedesktop.org/show_bug.cgi?id=3D10= 2322 might be about the same symptom - but using a different GPU architecture, a bleeding-edge new kernel, and I wanted to report this on the "amdgpu" driver (not Mesa), because amdgpu produces the only logged error messages, and if = the bug was in Mesa that would not explain why my system totally crashes (and n= ot just X11). --=20 You are receiving this mail because: You are the assignee for the bug.= --15032697310.aCC29A.998 Date: Sun, 20 Aug 2017 22:55:31 +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

Commen= t # 13 on bug 98874<= /a> from dwagner
Notice that my bug report https://bugs.freedesktop.org/show_bug.=
cgi?id=3D102322
might be about the same symptom - but using a different GPU architecture, a
bleeding-edge new kernel, and I wanted to report this on the "amdgpu&q=
uot; driver
(not Mesa), because amdgpu produces the only logged error messages, and if =
the
bug was in Mesa that would not explain why my system totally crashes (and n=
ot
just X11).


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