[Bug 89147] New: stuck on blitter ring GPU HANG: ecode 2:0x0000000a, in X
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Feb 14 07:18:23 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=89147
Bug ID: 89147
Summary: stuck on blitter ring GPU HANG: ecode 2:0x0000000a, in
X
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: harold at alum.mit.edu
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
The crash dump is zero bytes. Please let me know if other system details would
be useful. This is an Intel NUC, with a Broadwell CPU and Intel HD 5500
graphics. The version of Xorg is 1.17.1, the kernel version is 3.19, and the
version of Mesa is 10.4.4.
Feb 14 15:31:48 nuc kernel: [ 4432.007731] [drm] stuck on blitter ring
Feb 14 15:31:48 nuc kernel: [ 4432.008682] [drm] GPU HANG: ecode 2:0x0000000a,
in X [14298], reason: Ring hung, action: reset
Feb 14 15:31:48 nuc kernel: [ 4432.008686] [drm] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Feb 14 15:31:48 nuc kernel: [ 4432.008688] [drm] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Feb 14 15:31:48 nuc kernel: [ 4432.008690] [drm] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Feb 14 15:31:48 nuc kernel: [ 4432.008691] [drm] The gpu crash dump is required
to analyze gpu hangs, so please always attach it.
Feb 14 15:31:48 nuc kernel: [ 4432.008693] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Feb 14 15:32:00 nuc kernel: [ 4444.013939] [drm] stuck on blitter ring
Feb 14 15:32:00 nuc kernel: [ 4444.014795] [drm] GPU HANG: ecode 2:0x00000008,
in X [14298], reason: Ring hung, action: reset
Feb 14 15:32:00 nuc kernel: [ 4444.014864] [drm:i915_context_is_banned] *ERROR*
gpu hanging too fast, banning!
--
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/20150214/992c07bc/attachment.html>
More information about the intel-gfx-bugs
mailing list