[Bug 104520] Intermittent X crashes: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=104520

--- Comment #20 from hfekih at cannon.com ---
same problem here.
I am using Intel(R) Celeron(R) CPU  N3160
reproduced on Linux (kernel) 4.16.2 and 4.14.34, (Mesa 17.3.8)
problem can be reproduced by starting any application using OPEN GL ES

root at ca-linux:/home/cannon$ glmark2-es2-drm 
=======================================================
    glmark2 2014.03
=======================================================
    OpenGL Information
    GL_VENDOR:     Intel Open Source Technology Center
    GL_RENDERER:   Mesa DRI Intel(R) HD Graphics 400 (Braswell) 
    GL_VERSION:    OpenGL ES 3.1 Mesa 17.3.8
=======================================================
[build] use-vbo=false:i965: Failed to submit batchbuffer: Input/output error
----------------------------------------------------------------------------
dmesg output:
[   38.859784] [drm] GPU HANG: ecode 8:0:0xe757feff, in glmark2-es2-drm [346],
reason: Hang on rcs0, action: reset
[   38.859788] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[   38.859789] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[   38.859791] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[   38.859792] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[   38.859794] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   38.859869] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[   41.905511] i915 0000:00:02.0: Resetting chip after gpu hang
[   41.952424] asynchronous wait on fence i915:glmark2-es2-drm[346]/2:2 timed
out
[   47.072637] i915 0000:00:02.0: i915_reset_device timed out, cancelling all
in-flight rendering.
[   51.372311] i915 0000:00:02.0: Failed to reset chip

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20180418/610e43a2/attachment.html>