[Bug 80125] New: GPU hang: stuck on render ring
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jun 17 01:52:41 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=80125
Priority: medium
Bug ID: 80125
CC: intel-gfx-bugs at lists.freedesktop.org
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: GPU hang: stuck on render ring
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: mroos at linux.ee
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
Created attachment 101212
--> https://bugs.freedesktop.org/attachment.cgi?id=101212&action=edit
/sys/class/drm/card0/error
Found the fololowing hang info in dmesg:
[665416.152274] [drm] stuck on render ring
[665416.152277] [drm] stuck on blitter ring
[665416.152802] [drm] GPU HANG: ecode 0:0xf4e9fffe, in Xorg [1291], reason:
Ring hung, action: reset
[665416.152803] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[665416.152804] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[665416.152805] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[665416.152805] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[665416.152806] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[665416.152868] [drm:i915_context_is_banned] *ERROR* gpu hanging too fast,
banning!
[665418.152159] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
This happened on Sandy Bridge I5-2400 with Linux 3.15, Xord 7.7 from Debian
unstable 1:7.7+7 package. Uptime was 8 days and it's the first time I see this
kind of error so it's not easily reproducible.
Some days ago I also got these in dmesg - maybe related, maybe not.
[168707.005151] [drm:ilk_display_irq_handler] *ERROR* Pipe A FIFO underrun
[168707.152144] [drm:ilk_display_irq_handler] *ERROR* Pipe A FIFO underrun
--
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: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140617/a736f688/attachment.html>
More information about the intel-gfx-bugs
mailing list