<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [945 regression] 4.0-rc1 kernel GPU hang: ecode 3:0:0x02faffcf (i915) stuck on render ring ecode 3:0:0x02faffcf" href="https://bugs.freedesktop.org/show_bug.cgi?id=89334#c34">Comment # 34</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [945 regression] 4.0-rc1 kernel GPU hang: ecode 3:0:0x02faffcf (i915) stuck on render ring ecode 3:0:0x02faffcf" href="https://bugs.freedesktop.org/show_bug.cgi?id=89334">bug 89334</a> from <a class="email" href="mailto:nicepics13@operamail.com" title="Ben Hjelt <nicepics13@operamail.com>"> Ben Hjelt</a> <pre>Slackware -current (xf86-video-intel-git_20150824_3e07681) kernel 4.1.6 on an IBM T60: [ 1741.004033] [drm] stuck on render ring [ 1741.005028] [drm] GPU HANG: ecode 3:0:0x70efffc1, in Xorg [890], reason: Ring hung, action: reset [ 1741.005031] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 1741.005033] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 1741.005035] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 1741.005036] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 1741.005038] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 1741.315597] drm/i915: Resetting chip after gpu hang</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>