[Bug 90561] [SKL-Y] GPU hangs ecode 9:0:0x87cafff2/ecode 9:0:0x85dffffb while running benchmarks
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue May 26 05:43:45 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90561
--- Comment #7 from Ander Conselvan de Oliveira <conselvan2 at gmail.com> ---
(In reply to valtteri.rantala from comment #6)
> Later with the additional test causes a system hang.
> Here are new dmesg.
> [ 167.712499] [drm] stuck on render ring
> [ 167.714151] [drm] GPU HANG: ecode 9:0:0x85dffffb, in synmark2 [3031],
> reason:
> Ring hung, action: reset
> [ 167.714157] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
> stack, including userspace.
> [ 167.714159] [drm] Please file a _new_ bug report on bugs.freedesktop.org
> against DRI -> DRM/Intel
> [ 167.714161] [drm] drm/i915 developers can then reassign to the right
> component if it's not a kernel issue.
> [ 167.714163] [drm] The gpu crash dump is required to analyze gpu hangs, so
> please always attach it.
> [ 167.714165] [drm] GPU crash dump saved to /sys/class/drm/card0/error
> [ 167.716498] drm/i915: Resetting chip after gpu hang
> [ 168.182886] [drm] RC6 on
> [ 175.719839] [drm] stuck on render ring
> [ 175.721031] [drm] GPU HANG: ecode 9:0:0x87cafff2, in synmark2 [3032],
> reason: Ring hung, action: reset
> [ 175.723310] drm/i915: Resetting chip after gpu hang
> [ 176.189345] [drm] RC6 on
> [ 261.507979] [drm:fw_domains_get [i915]] *ERROR* blitter: timed out
> waiting for forcewake ack request.
> [ 262.510760] [drm:fw_domains_get [i915]] *ERROR* blitter: timed out
> waiting for forcewake ack request.
> [ 262.732373] [drm:fw_domains_get [i915]] *ERROR* media: timed out waiting
> for forcewake ack request.
This system hang looks like bug 89959.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150526/331076bc/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list