[Bug 95145] New: GPU HANG: ecode 9:0:0x84dffff8, in X [1481], reason: Ring hung, action: reset

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 95145
           Summary: GPU HANG: ecode 9:0:0x84dffff8, in X [1481], reason:
                    Ring hung, action: reset
           Product: DRI
           Version: XOrg git
          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: bugs.freedesktop.org at r123.de
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 123268
  --> https://bugs.freedesktop.org/attachment.cgi?id=123268&action=edit
Xorg.0.log

Steps to reproduce for me:
1. Start X
2. Start Eclipse
3. About 10-20s after starting Eclipse the error occurs

Used software versions:
Gentoo Linux
Kernel 4.5.2 / x86_64 Intel(R) Core(TM) i5-6440HQ CPU @ 2.60GHz
xorg-server 1.18.3
Intel driver 2.99.917_p20160423
Nesa 11.2.1

dmesg output when error occurs:

[Di Apr 26 11:07:57 2016] [drm] stuck on render ring
[Di Apr 26 11:07:57 2016] [drm] GPU HANG: ecode 9:0:0x84dffff8, in X [1481],
reason: Ring hung, action: reset
[Di Apr 26 11:07:57 2016] [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
[Di Apr 26 11:07:57 2016] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[Di Apr 26 11:07:57 2016] [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
[Di Apr 26 11:07:57 2016] [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
[Di Apr 26 11:07:57 2016] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
[Di Apr 26 11:07:57 2016] drm/i915: Resetting chip after gpu hang
[Di Apr 26 11:07:59 2016] [drm] RC6 on
[Di Apr 26 11:08:03 2016] [drm] stuck on render ring
[Di Apr 26 11:08:03 2016] [drm] GPU HANG: ecode 9:0:0x84dffff8, in X [1481],
reason: Ring hung, action: reset
[Di Apr 26 11:08:03 2016] [drm:i915_set_reset_status] *ERROR* gpu hanging too
fast, banning!
[Di Apr 26 11:08:03 2016] drm/i915: Resetting chip after gpu hang
[Di Apr 26 11:08:05 2016] [drm] RC6 on


Relevant Xorg.0.log output:

[     8.693] (II) intel(0): EDID vendor "MEI", prod id 38562
[     8.693] (II) intel(0):     EDID quirk: Use maximum size instead of
detailed timing sizes.
[     8.693] (II) intel(0): Using EDID range info for horizontal sync
[     8.693] (II) intel(0): Using EDID range info for vertical refresh
[     8.693] (II) intel(0): Printing DDC gathered Modelines:
[     8.693] (II) intel(0): Modeline "2560x1440"x0.0  257.54  2560 2648 2680
2800  1440 1468 1473 1533 +hsync +vsync (92.0 kHz eP)
[     8.693] (II) intel(0): Modeline "2560x1440"x0.0  257.51  2560 2648 2680
2800  1440 1468 1473 1916 +hsync +vsync (92.0 kHz e)
[     8.989] (II) intel(0): resizing framebuffer to 4480x1440
[     9.015] (II) intel(0): switch to mode 1920x1200 at 60.0 on DP3-1 using pipe
1, position (2560, 240), rotation normal, reflection none
[   108.709] (EE) intel(0): Failed to submit rendering commands (Input/output
error), disabling acceleration.
[   108.709] (EE) intel(0): When reporting this, please include
/sys/class/drm/card0/error and the full dmesg.


Full Xorg.0.log and /sys/class/drm/card0/error are attached.

-- 
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/20160426/7c18c101/attachment-0001.html>