From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105819] Window system hang due to GPU Fault
Date: Sat, 15 Sep 2018 22:22:04 +0000 [thread overview]
Message-ID: <bug-105819-502-4y8ZTywmoD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105819-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1640 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105819
--- Comment #8 from Greg White <gwhite@kupulau.com> ---
Same here, Vega 56 / kernel 4.19rc3. Tried mesa 18.3 master and 18.2, llvm 8
(svn) and llvm 6 on Arch linux; libdrm is all at current git head. This
reproduces very easily and quickly using chrome and the webgl fish demo, but
hangs will occur within a few minutes just browsing with chrome.
[ 252.184802] amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0 ring:157
vmid:5 pasid:32775, for process chrome pid 1716 thread chrome --t:cs0 pid 1769
)
[ 252.184806] amdgpu 0000:0d:00.0: at address 0x000080011680c000 from 27
[ 252.184807] amdgpu 0000:0d:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0050113B
[ 252.184811] amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0 ring:157
vmid:5 pasid:32775, for process chrome pid 1716 thread chrome --t:cs0 pid 1769
)
[ 252.184813] amdgpu 0000:0d:00.0: at address 0x000080011680c000 from 27
[ 252.184814] amdgpu 0000:0d:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 252.184818] amdgpu 0000:0d:00.0: [gfxhub] VMC page fault (src_id:0 ring:157
vmid:5 pasid:32775, for process chrome pid 1716 thread chrome --t:cs0 pid 1769
)
[ 252.184820] amdgpu 0000:0d:00.0: at address 0x000080011680c000 from 27
[ 252.184821] amdgpu 0000:0d:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 262.385344] [drm:amdgpu_job_timedout] *ERROR* ring gfx timeout, signaled
seq=50421, emitted seq=50423
[ 262.385347] [drm] GPU recovery disabled.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2392 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-09-15 22:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 17:59 [Bug 105819] Window system hang due to GPU Fault bugzilla-daemon
2018-03-31 22:34 ` bugzilla-daemon
2018-04-12 10:52 ` bugzilla-daemon
2018-04-30 2:44 ` bugzilla-daemon
2018-05-20 6:28 ` bugzilla-daemon
2018-06-30 17:42 ` bugzilla-daemon
2018-07-01 16:08 ` bugzilla-daemon
2018-07-04 12:29 ` bugzilla-daemon
2018-09-15 22:22 ` bugzilla-daemon [this message]
2018-09-18 2:11 ` bugzilla-daemon
2019-01-12 17:22 ` bugzilla-daemon
2019-04-26 1:54 ` bugzilla-daemon
2019-05-07 12:19 ` bugzilla-daemon
2019-11-17 5:11 ` bugzilla-daemon
2019-11-19 8:33 ` 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-105819-502-4y8ZTywmoD@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