<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [hsw] GPU hang on first context use (after long uptime)" href="https://bugs.freedesktop.org/show_bug.cgi?id=97020#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [hsw] GPU hang on first context use (after long uptime)" href="https://bugs.freedesktop.org/show_bug.cgi?id=97020">bug 97020</a> from <a class="email" href="mailto:nick@reloco.com.ar" title="Nicolás Lichtmaier <nick@reloco.com.ar>"> Nicolás Lichtmaier</a> <pre>Created <a href="attachment.cgi?id=126031" name="attach_126031" title="Another dump">attachment 126031</a> <a href="attachment.cgi?id=126031&action=edit" title="Another dump">[details]</a> Another dump This keeps happening, here's another /sys/class/drm/card0/error dump. This happened when the computer was resuming after suspension. In dmesg: [215029.932383] [drm] stuck on render ring [215029.933531] [drm] GPU HANG: ecode 7:0:0x84dfbffe, in chrome [7937], reason: Ring hung, action: reset [215029.933533] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [215029.933534] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [215029.933536] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [215029.933537] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [215029.933538] [drm] GPU crash dump saved to /sys/class/drm/card0/error [215029.935896] drm/i915: Resetting chip after gpu hang</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>