From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 107152] GPU fault detected: 146 / VM_CONTEXT1_PROTECTION_FAULT / ring gfx timeout Date: Fri, 03 Aug 2018 23:48:14 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1676118392==" 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 D996689C08 for ; Fri, 3 Aug 2018 23:48:13 +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 --===============1676118392== Content-Type: multipart/alternative; boundary="15333400932.97c2FEeC.30083" Content-Transfer-Encoding: 7bit --15333400932.97c2FEeC.30083 Date: Fri, 3 Aug 2018 23:48:13 +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=3D107152 --- Comment #10 from dwagner --- (In reply to Andrey Grodzovsky from comment #8) > dwanger, i think you already have all the trace tools installed from > previous debug sessions so this should be quick for you Yes, and I tried really hard (with above attached script run as "root" on a text console while the "othan_test.sh" script played the video on the scree= n) to catch any useful output, but that failed for the same reason I mentioned= in https://bugs.freedesktop.org/show_bug.cgi?id=3D102322#c20 - the system simply crashes too hard to quickly to be able to do anything a= fter amdgpu.ko crashes. The output I get in gpu_result.txt stops at the "waiting= for the crash" line. It is only in about 1 out of 10 crashes that the syslog at least contains t= he error messages from the amdgpu crash, in the other 90% of cases the same cr= ash occurs with no message being recorded at all. If there was any method to let other processes survive for a while after am= dgpu crashes, please let me know. --=20 You are receiving this mail because: You are the assignee for the bug.= --15333400932.97c2FEeC.30083 Date: Fri, 3 Aug 2018 23:48:13 +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 # 10 on bug 10715= 2 from dwagner

(In reply to Andrey Grodzovsky from comment #8)
> dwanger, i think you already have all the trace =
tools installed from
> previous debug sessions so this should be quick for you
Yes, and I tried really hard (with above attached script run as "root&=
quot; on a
text console while the "othan_test.sh" script played the video on=
 the screen)
to catch any useful output, but that failed for the same reason I mentioned=
 in
https://bugs.freedesktop.org/show_=
bug.cgi?id=3D102322#c20
- the system simply crashes too hard to quickly to be able to do anything a=
fter
amdgpu.ko crashes. The output I get in gpu_result.txt stops at the "wa=
iting for
the crash" line.

It is only in about 1 out of 10 crashes that the syslog at least contains t=
he
error messages from the amdgpu crash, in the other 90% of cases the same cr=
ash
occurs with no message being recorded at all.

If there was any method to let other processes survive for a while after am=
dgpu
crashes, please let me know.

You are receiving this mail because:

You are the assignee for the bug.

= --15333400932.97c2FEeC.30083-- --===============1676118392== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1676118392==--