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: Wed, 22 Aug 2018 22:18:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0621500812==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0D6DF6E45A for ; Wed, 22 Aug 2018 22:18:11 +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 --===============0621500812== Content-Type: multipart/alternative; boundary="15349762910.e4fA.2619" Content-Transfer-Encoding: 7bit --15349762910.e4fA.2619 Date: Wed, 22 Aug 2018 22:18:10 +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 #61 from dwagner --- > Please use amdgpu.vm_update_mode=3D3 to get back to VM_FAULTs issue. The "good" news is that reproduction of the crashes with 3-fps-video-replay= is very quick when using amdgpu.vm_update_mode=3D3. But the bad news is that I have not been able to get useful error output wh= en using vm_update_mode=3D3. At first I tried with also amdgpu.vm_debug=3D1, and with that in 10 crashes= not a single error output line was emitted to either the ssh channel or the system journal. I then tried with amdgpu.vm_debug=3D0, and while a few error lines output b= ecome logged, then, not quite anything useful - see also in attached example: [ 912.447139] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D12818, emitted seq=3D12819 [ 912.447145] [drm] GPU recovery disabled. These are the only lines indicating the error, not even the echo "crash detected!" after the "dmesg -w | tee /dev/tty | grep -m 1 -e "amdgpu.*GPU" -e "amdgpu.*ERROR" gets emitted, much less the theoretically following umr commands. What could I do to not let the kernel die so quickly when using amdgpu.vm_update_mode=3D3? --=20 You are receiving this mail because: You are the assignee for the bug.= --15349762910.e4fA.2619 Date: Wed, 22 Aug 2018 22:18:11 +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 # 61 on bug 10232= 2 from dwagner 
> Please use amdgpu.vm_update_mode=3D=
3 to get back to VM_FAULTs issue.

The "good" news is that reproduction of the crashes with 3-fps-vi=
deo-replay is
very quick when using amdgpu.vm_update_mode=3D3.

But the bad news is that I have not been able to get useful error output wh=
en
using vm_update_mode=3D3.

At first I tried with also amdgpu.vm_debug=3D1, and with that in 10 crashes=
 not a
single error output line was emitted to either the ssh channel or the system
journal.

I then tried with amdgpu.vm_debug=3D0, and while a few error lines output b=
ecome
logged, then, not quite anything useful - see also in attached example:

[  912.447139] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=3D12818, emitted seq=3D12819
[  912.447145] [drm] GPU recovery disabled.

These are the only lines indicating the error, not even the
 echo "crash detected!"
after the
 "dmesg -w | tee /dev/tty | grep -m 1 -e "amdgpu.*GPU" -e &q=
uot;amdgpu.*ERROR"
gets emitted, much less the theoretically following umr commands.

What could I do to not let the kernel die so quickly when using
amdgpu.vm_update_mode=3D3?

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