[Bug 96281] New: [drm] GPU HANG: ecode 9:0:0x85dffffb, in csgo_linux64 [3821], reason: Engine(s) hung, action: reset (NUC6i7KYK)

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 96281
           Summary: [drm] GPU HANG: ecode 9:0:0x85dffffb, in csgo_linux64
                    [3821], reason: Engine(s) hung, action: reset
                    (NUC6i7KYK)
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: p at article.se
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 124191
  --> https://bugs.freedesktop.org/attachment.cgi?id=124191&action=edit
/sys/class/drm/card0/error

Hardware: NUC6i7KYK (i7-6770HQ)
OS: Debian stretch

Same problem with default kernel in stretch (linux-image-4.5.0-2-amd64
4.5.4-1), 4.6 from experimental (linux-image-4.6.0-trunk-amd64 4.6-1~exp1) as
well as what I'm doing this bugreport with; drm-intel-nightly:
2016y-05m-30d-17h-51m-33s, built from git.

Running mesa 11.2.2-1 and xserver-xorg-video-intel 2:2.99.917+git20160522-1,
all from stretch.

...
[  160.897606] [drm] RC6 on
[  169.886045] [drm] stuck on render ring
[  169.888450] [drm] GPU HANG: ecode 9:0:0xfffffffe, in csgo_linux64 [1172],
reason: Engine(s) hung, action: reset
[  169.888516] [drm:i915_reset_and_wakeup] resetting chip
[  169.890965] drm/i915: Resetting chip after gpu hang
...

Attaching full kernel output (*very* verbose from drm.debug=0x1e) as well as
card0/error output.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160530/b08129fc/attachment.html>