[Bug 95312] New: 4.6-rc5: [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat May 7 20:49:31 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=95312
Bug ID: 95312
Summary: 4.6-rc5: [drm] GPU HANG: ecode 6:-1:0x00000000,
reason: Kicking stuck wait 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: mmokrejs at fold.natur.cuni.cz
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 123539
--> https://bugs.freedesktop.org/attachment.cgi?id=123539&action=edit
/sys/class/drm/card0/error
This could be a dupe of bug #93710 (same hardware, same kernel .config and
without explicit intel_iommu=off).
[798005.164877] snd_hda_intel 0000:00:1b.0: IRQ timing workaround is activated
for card #0. Suggest a bigger bdl_pos_adj.
[800008.420528] [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck
wait on render ring, action: continue
[800008.420592] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[800008.420593] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[800008.420594] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[800008.420595] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[800008.420596] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[848558.214001] kmemleak: 1 new suspected memory leaks (see
/sys/kernel/debug/kmemleak)
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list 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/20160507/4a36a4d9/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list