From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 00:24:35 +0000 [thread overview]
Message-ID: <bug-102322-502-lJZza2CImz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102322-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 3653 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #58 from dwagner <jb5sgc1n.nya@20mm.eu> ---
Here comes another trace log, with your info2.patch applied.
Something must have changed since the last test, as it took pretty long this
time to reproduce the crash. Could that have been caused by
https://cgit.freedesktop.org/~agd5f/linux/commit/drivers/gpu/drm/amd/amdgpu/nbio_v7_4.c?h=amd-staging-drm-next&id=b385925f3922faca7435e50e31380bb2602fd6b8
now being part of the kernel?
However, the latest trace you find attached below is not much different to the
last one, xzcat /tmp/gpu_debug5.txt.xz | grep '^\[' will tell you:
[ 1510.023112] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=475104, emitted seq=475106
[ 1510.023117] [drm] GPU recovery disabled.
amdgpu_cs:0-806 [012] .... 1787.493126: amdgpu_vm_bo_cs:
soffs=00001001a0, eoffs=00001001b9, flags=70
amdgpu_cs:0-806 [012] .... 1787.493127: amdgpu_vm_bo_cs:
soffs=0000100200, eoffs=00001021e0, flags=70
amdgpu_cs:0-806 [012] .... 1787.493127: amdgpu_vm_bo_cs:
soffs=0000102200, eoffs=00001041e0, flags=70
amdgpu_cs:0-806 [012] .... 1787.493129: amdgpu_vm_bo_cs:
soffs=000010c1e0, eoffs=000010c2e1, flags=70
amdgpu_cs:0-806 [012] .... 1787.493131: drm_sched_job:
entity=00000000406345a7, id=10239, fence=000000007a120377, ring=gfx, job
count:8, hw job count:0
And later in the file you can find:
------------------------------------------------------
crash detected!
executing umr -O halt_waves -wa
No active waves!
executing umr -O verbose -R gfx[.]
polaris11.gfx.rptr == 512
polaris11.gfx.wptr == 512
polaris11.gfx.drv_wptr == 512
polaris11.gfx.ring[ 481] == 0xffff1000 ...
polaris11.gfx.ring[ 482] == 0xffff1000 ...
polaris11.gfx.ring[ 483] == 0xffff1000 ...
polaris11.gfx.ring[ 484] == 0xffff1000 ...
polaris11.gfx.ring[ 485] == 0xffff1000 ...
polaris11.gfx.ring[ 486] == 0xffff1000 ...
polaris11.gfx.ring[ 487] == 0xffff1000 ...
polaris11.gfx.ring[ 488] == 0xffff1000 ...
polaris11.gfx.ring[ 489] == 0xffff1000 ...
polaris11.gfx.ring[ 490] == 0xffff1000 ...
polaris11.gfx.ring[ 491] == 0xffff1000 ...
polaris11.gfx.ring[ 492] == 0xffff1000 ...
polaris11.gfx.ring[ 493] == 0xffff1000 ...
polaris11.gfx.ring[ 494] == 0xffff1000 ...
polaris11.gfx.ring[ 495] == 0xffff1000 ...
polaris11.gfx.ring[ 496] == 0xffff1000 ...
polaris11.gfx.ring[ 497] == 0xffff1000 ...
polaris11.gfx.ring[ 498] == 0xffff1000 ...
polaris11.gfx.ring[ 499] == 0xffff1000 ...
polaris11.gfx.ring[ 500] == 0xffff1000 ...
polaris11.gfx.ring[ 501] == 0xffff1000 ...
polaris11.gfx.ring[ 502] == 0xffff1000 ...
polaris11.gfx.ring[ 503] == 0xffff1000 ...
polaris11.gfx.ring[ 504] == 0xffff1000 ...
polaris11.gfx.ring[ 505] == 0xffff1000 ...
polaris11.gfx.ring[ 506] == 0xffff1000 ...
polaris11.gfx.ring[ 507] == 0xffff1000 ...
polaris11.gfx.ring[ 508] == 0xffff1000 ...
polaris11.gfx.ring[ 509] == 0xffff1000 ...
polaris11.gfx.ring[ 510] == 0xffff1000 ...
polaris11.gfx.ring[ 511] == 0xffff1000 ...
polaris11.gfx.ring[ 512] == 0xc0032200 rwD
trying to get ADR from dmesg output for 'umr -O verbose -vm ...'
trying to get VMID from dmesg output for 'umr -O verbose -vm ...'
done after crash.
-------------------------------------------
So even without GPU reset, still no "waves". And the error message also does
not state any VM fault address.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4724 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-08-22 0:24 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 22:53 [Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung! bugzilla-daemon
2017-11-19 16:40 ` bugzilla-daemon
2018-02-24 18:36 ` bugzilla-daemon
2018-06-03 21:00 ` bugzilla-daemon
2018-06-03 21:02 ` bugzilla-daemon
2018-06-25 21:43 ` bugzilla-daemon
2018-06-25 22:11 ` bugzilla-daemon
2018-06-25 23:08 ` bugzilla-daemon
2018-06-26 15:20 ` bugzilla-daemon
2018-06-26 15:21 ` bugzilla-daemon
2018-06-26 22:52 ` bugzilla-daemon
2018-06-27 7:48 ` bugzilla-daemon
2018-06-27 13:53 ` bugzilla-daemon
2018-06-27 23:15 ` bugzilla-daemon
2018-06-28 2:17 ` bugzilla-daemon
2018-06-28 4:17 ` bugzilla-daemon
2018-06-28 4:36 ` bugzilla-daemon
2018-06-28 10:33 ` bugzilla-daemon
2018-06-28 19:56 ` bugzilla-daemon
2018-06-28 21:09 ` bugzilla-daemon
2018-06-28 22:56 ` bugzilla-daemon
2018-06-28 22:57 ` bugzilla-daemon
2018-06-29 0:10 ` bugzilla-daemon
2018-07-04 23:03 ` bugzilla-daemon
2018-07-05 13:59 ` bugzilla-daemon
2018-07-05 23:32 ` bugzilla-daemon
2018-07-06 23:20 ` bugzilla-daemon
2018-07-07 8:36 ` bugzilla-daemon
2018-07-07 20:08 ` bugzilla-daemon
2018-07-09 14:34 ` bugzilla-daemon
2018-07-11 22:32 ` bugzilla-daemon
2018-07-15 8:56 ` bugzilla-daemon
2018-07-15 9:03 ` bugzilla-daemon
2018-07-15 9:07 ` bugzilla-daemon
2018-07-15 19:59 ` bugzilla-daemon
2018-07-16 14:06 ` bugzilla-daemon
2018-07-29 10:02 ` bugzilla-daemon
2018-08-08 23:07 ` bugzilla-daemon
2018-08-09 20:56 ` bugzilla-daemon
2018-08-14 21:27 ` bugzilla-daemon
2018-08-15 14:24 ` bugzilla-daemon
2018-08-15 22:03 ` bugzilla-daemon
2018-08-16 21:53 ` bugzilla-daemon
2018-08-16 21:55 ` bugzilla-daemon
2018-08-16 21:56 ` bugzilla-daemon
2018-08-16 21:57 ` bugzilla-daemon
2018-08-16 22:31 ` bugzilla-daemon
2018-08-17 21:25 ` bugzilla-daemon
2018-08-18 21:36 ` bugzilla-daemon
2018-08-18 21:37 ` bugzilla-daemon
2018-08-18 21:38 ` bugzilla-daemon
2018-08-18 21:40 ` bugzilla-daemon
2018-08-18 21:43 ` bugzilla-daemon
2018-08-20 14:16 ` bugzilla-daemon
2018-08-21 8:41 ` bugzilla-daemon
2018-08-21 14:43 ` bugzilla-daemon
2018-08-21 21:16 ` bugzilla-daemon
2018-08-21 21:29 ` bugzilla-daemon
2018-08-22 0:24 ` bugzilla-daemon [this message]
2018-08-22 0:26 ` bugzilla-daemon
2018-08-22 14:33 ` bugzilla-daemon
2018-08-22 22:18 ` bugzilla-daemon
2018-08-22 22:18 ` bugzilla-daemon
2018-09-19 23:35 ` bugzilla-daemon
2018-09-19 23:35 ` bugzilla-daemon
2018-09-23 22:04 ` bugzilla-daemon
2018-09-23 23:42 ` bugzilla-daemon
2018-09-25 12:11 ` bugzilla-daemon
2018-11-14 0:23 ` bugzilla-daemon
2018-11-15 23:37 ` bugzilla-daemon
2018-11-15 23:38 ` bugzilla-daemon
2018-11-15 23:39 ` bugzilla-daemon
2018-12-17 22:56 ` bugzilla-daemon
2018-12-22 20:41 ` bugzilla-daemon
2018-12-24 12:56 ` bugzilla-daemon
2018-12-24 14:49 ` bugzilla-daemon
2019-01-19 17:01 ` bugzilla-daemon
2019-02-16 15:06 ` bugzilla-daemon
2019-04-11 6:40 ` bugzilla-daemon
2019-04-12 22:11 ` bugzilla-daemon
2019-04-12 23:00 ` bugzilla-daemon
2019-04-13 13:27 ` bugzilla-daemon
2019-06-03 20:03 ` bugzilla-daemon
2019-07-08 7:51 ` bugzilla-daemon
2019-07-09 7:38 ` bugzilla-daemon
2019-07-09 21:50 ` bugzilla-daemon
2019-09-07 5:42 ` bugzilla-daemon
2019-09-12 23:09 ` bugzilla-daemon
2019-09-25 21:37 ` bugzilla-daemon
2019-09-26 8:35 ` bugzilla-daemon
2019-09-26 12:29 ` bugzilla-daemon
2019-11-19 8:22 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-102322-502-lJZza2CImz@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).