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: Thu, 15 Nov 2018 23:37:57 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0654535591==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 006676E532 for ; Thu, 15 Nov 2018 23:37: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 --===============0654535591== Content-Type: multipart/alternative; boundary="15423250761.3B08.19827" Content-Transfer-Encoding: 7bit --15423250761.3B08.19827 Date: Thu, 15 Nov 2018 23:37: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=3D102322 --- Comment #69 from dwagner --- As promised in above comment, today I ran my debug script "gpu_debug4.sh" to obtain the diagnostic output after the crash as requested above. This output is in attached "gpu_debug4_output.txt". Since the trace output, the "dmesg -w" output and stdout are written to the same file, they are roughly chronologic. If you want to look only at the dmesg-output, use > grep '^\[' gpu_debug4_output.txt (gpu_debug4.sh is a slight variation of earlier gpu_debug3.sh, just writing= to a local log file.) BTW: I ran the script multiple times, crashes occurred after 5 to 300 secon= ds, the diagnostic output always looked like in attached gpu_debug4_output.txt. --=20 You are receiving this mail because: You are the assignee for the bug.= --15423250761.3B08.19827 Date: Thu, 15 Nov 2018 23:37: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 # 69 on bug 10232= 2 from dwagner 
As promised in above comment, today I ran my debug script &quo=
t;gpu_debug4.sh" to
obtain the diagnostic output after the crash as requested above.
This output is in attached "gpu_debug4_output.txt".
Since the trace output, the "dmesg -w" output and stdout are writ=
ten to the
same file, they are roughly chronologic.

If you want to look only at the dmesg-output, use
> grep '^\[' gpu_debug4_output.txt

(gpu_debug4.sh is a slight variation of earlier gpu_debug3.sh, just writing=
 to
a local log file.)

BTW: I ran the script multiple times, crashes occurred after 5 to 300 secon=
ds,
the diagnostic output always looked like in attached gpu_debug4_output.txt.=

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