<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW] GPU error state gathered while decoding 4K video with VA-API and displaying via an OpenGL compositor" href="https://bugs.freedesktop.org/show_bug.cgi?id=80802#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HSW] GPU error state gathered while decoding 4K video with VA-API and displaying via an OpenGL compositor" href="https://bugs.freedesktop.org/show_bug.cgi?id=80802">bug 80802</a> from <a class="email" href="mailto:simon@farnz.org.uk" title="Simon Farnsworth <simon@farnz.org.uk>"> Simon Farnsworth</a> <pre>Created <a href="attachment.cgi?id=102128" name="attach_102128" title="Compressed error state">attachment 102128</a> <a href="attachment.cgi?id=102128&action=edit" title="Compressed error state">[details]</a> Compressed error state This is the error state; dmesg to go with it says: [ 2964.222067] [drm] stuck on render ring [ 2964.222090] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 2964.222102] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 2964.222114] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 2964.222119] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 2964.222125] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.</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> </ul> </body> </html>