[Bug 106119] New: GPU Hang Triage (GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue)
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Apr 18 07:44:26 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=106119
Bug ID: 106119
Summary: GPU Hang Triage (GPU HANG: ecode 6:-1:0x00000000,
reason: Kicking stuck semaphore on render ring,
action: continue)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: ajp at ohno.lol
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 138898
--> https://bugs.freedesktop.org/attachment.cgi?id=138898&action=edit
What I was told to attach by dmesg
[drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on
render ring, action: continue
[231430.174287] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[231430.174287] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[231430.174288] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[231430.174289] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[231430.174290] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[232408.242876] kworker/dying (16698) used greatest stack depth: 10936 bytes
left
I saw this on another thread:
can you reproduce issue with "drm.debug=0xe" in your boot command line and then
attached your dmesg.
So I'll do that too, but it's an "I don't know how to reproduce it but I know
it'll happen again" type thing.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180418/17c2c5de/attachment.html>
More information about the intel-gfx-bugs
mailing list