From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107152] GPU fault detected: 146 / VM_CONTEXT1_PROTECTION_FAULT / ring gfx timeout
Date: Tue, 31 Jul 2018 21:41:14 +0000 [thread overview]
Message-ID: <bug-107152-502-hxpKc1gdL6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107152-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2018 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107152
--- Comment #4 from dwagner <jb5sgc1n.nya@20mm.eu> ---
Saw this kind of crash (still with the latest amd-staging-drm-next kernel)
three times in a row today, just by playing a specific video immediately after
rebooting and starting X11 with mpv, before the 10 minute video ended.
The video (which just shows a static cover image) can be obtained via:
youtube-dl -f 248+251 'https://www.youtube.com/watch?v=kYKE78Pcjog'
The log messages were just like reported above, I guess the additional "hw_done
or flip_done timed out" after the "GPU reset begin!" is not really relevant:
Jul 31 22:20:21 ryzen kernel: amdgpu 0000:0a:00.0: GPU fault detected: 147
0x0f580402 for process Xorg pid 793 thread amdgpu_cs:0 pid 794
Jul 31 22:20:21 ryzen kernel: amdgpu 0000:0a:00.0:
VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0010C3EB
Jul 31 22:20:21 ryzen kernel: amdgpu 0000:0a:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02004002
Jul 31 22:20:21 ryzen kernel: amdgpu 0000:0a:00.0: VM fault (0x02, vmid 1,
pasid 32768) at page 1098731, read from 'TC3' (0x54433300) (4)
Jul 31 22:20:21 ryzen kernel: amdgpu 0000:0a:00.0: GPU fault detected: 146
0x0c984424 for process Xorg pid 793 thread amdgpu_cs:0 pid 794
Jul 31 22:20:21 ryzen kernel: amdgpu 0000:0a:00.0:
VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00100193
Jul 31 22:20:21 ryzen kernel: amdgpu 0000:0a:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04044024
Jul 31 22:20:21 ryzen kernel: amdgpu 0000:0a:00.0: VM fault (0x24, vmid 2,
pasid 32768) at page 1048979, read from 'TC1' (0x54433100) (68)
Jul 31 22:20:25 ryzen kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
gfx timeout, signaled seq=26570, emitted seq=26573
Jul 31 22:20:25 ryzen kernel: amdgpu 0000:0a:00.0: GPU reset begin!
Jul 31 22:20:35 ryzen kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR*
[CRTC:44:crtc-0] hw_done or flip_done timed out
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2923 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-07-31 21:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 20:03 [Bug 107152] GPU fault detected: 146 / VM_CONTEXT1_PROTECTION_FAULT / ring gfx timeout bugzilla-daemon
2018-07-07 20:04 ` bugzilla-daemon
2018-07-07 20:05 ` bugzilla-daemon
2018-07-30 21:12 ` bugzilla-daemon
2018-07-31 21:41 ` bugzilla-daemon [this message]
2018-07-31 21:45 ` bugzilla-daemon
2018-08-02 21:25 ` bugzilla-daemon
2018-08-02 21:54 ` bugzilla-daemon
2018-08-03 16:54 ` bugzilla-daemon
2018-08-03 23:42 ` bugzilla-daemon
2018-08-03 23:48 ` bugzilla-daemon
2018-08-05 19:59 ` bugzilla-daemon
2018-08-08 23:13 ` bugzilla-daemon
2018-08-09 16:25 ` bugzilla-daemon
2018-08-09 20:56 ` bugzilla-daemon
2019-01-24 6:45 ` 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-107152-502-hxpKc1gdL6@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).