<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - stuck on render ring (v4.7-rc7 Sky Lake Integrated Graphics [8086:1916])" href="https://bugs.freedesktop.org/show_bug.cgi?id=96894#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - stuck on render ring (v4.7-rc7 Sky Lake Integrated Graphics [8086:1916])" href="https://bugs.freedesktop.org/show_bug.cgi?id=96894">bug 96894</a> from <a class="email" href="mailto:bjorn@mork.no" title="Bjørn Mork <bjorn@mork.no>"> Bjørn Mork</a> <pre>Created <a href="attachment.cgi?id=129008" name="attach_129008" title="xorg.log from GPU HANG with modeset, Mesa 13.0.3 and Linux v4.10-rc4">attachment 129008</a> <a href="attachment.cgi?id=129008&action=edit" title="xorg.log from GPU HANG with modeset, Mesa 13.0.3 and Linux v4.10-rc4">[details]</a> xorg.log from GPU HANG with modeset, Mesa 13.0.3 and Linux v4.10-rc4 This is the log with the actual GPU HANG event, as you can see by matching up the Modeline log lines with the timing of the GPU resets: [19308.656674] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1171], reason: Hang on render ring, action: reset [19308.656769] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [19308.656770] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [19308.656771] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [19308.656772] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [19308.656773] [drm] GPU crash dump saved to /sys/class/drm/card0/error [19308.657131] drm/i915: Resetting chip after gpu hang [19308.657752] [drm] RC6 on [19308.677139] [drm] GuC firmware load skipped [19328.645312] drm/i915: Resetting chip after gpu hang [19328.649380] [drm] RC6 on [19328.668497] [drm] GuC firmware load skipped [19348.612672] drm/i915: Resetting chip after gpu hang [19348.613017] [drm] RC6 on [19348.630830] [drm] GuC firmware load skipped [19364.612475] drm/i915: Resetting chip after gpu hang [19364.614544] [drm] RC6 on [19364.629781] [drm] GuC firmware load skipped [19382.660101] drm/i915: Resetting chip after gpu hang [19382.660955] [drm] RC6 on [19382.680661] [drm] GuC firmware load skipped [19402.628876] drm/i915: Resetting chip after gpu hang [19402.629229] [drm] RC6 on [19402.643134] [drm] GuC firmware load skipped [19422.660054] drm/i915: Resetting chip after gpu hang [19422.660419] [drm] RC6 on [19422.675415] [drm] GuC firmware load skipped [19440.644097] drm/i915: Resetting chip after gpu hang [19440.644558] [drm] RC6 on [19440.663878] [drm] GuC firmware load skipped [19458.627752] drm/i915: Resetting chip after gpu hang [19458.634024] [drm] RC6 on [19458.650700] [drm] GuC firmware load skipped [19478.659877] drm/i915: Resetting chip after gpu hang [19478.665303] [drm] RC6 on [19478.684634] [drm] GuC firmware load skipped [19498.627632] drm/i915: Resetting chip after gpu hang [19498.634862] [drm] RC6 on [19498.653638] [drm] GuC firmware load skipped [19510.659670] drm/i915: Resetting chip after gpu hang [19510.665894] [drm] RC6 on [19510.680479] [drm] GuC firmware load skipped</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>