[Bug 96901] New: GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 96901
           Summary: GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck
                    semaphore on render ring, action: continue
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: liori at o2.pl
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 125030
  --> https://bugs.freedesktop.org/attachment.cgi?id=125030&action=edit
sudo cat /sys/class/drm/card0/error | xz

[47139.652943] [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck
semaphore on render ring, action: continue
[47139.652946] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[47139.652946] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[47139.652947] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[47139.652948] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[47139.652948] [drm] GPU crash dump saved to /sys/class/drm/card0/error

liori at liori-pc:~$ uname -a
Linux liori-pc 4.6.0-0.bpo.1-amd64 #1 SMP Debian 4.6.1-1~bpo8+1 (2016-06-14)
x86_64 GNU/Linux

Distribution: Debian Jessie with enabled official backports.

Motherboard: Gigabyte Z68X-UD3H-B3

Screens: one 1920x1080 screen on HDMI.

-- 
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/20160712/2ba79211/attachment.html>