<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [SNB 4.8] gpu at 0x7955b000, but request was 0x77b0b000" href="https://bugs.freedesktop.org/show_bug.cgi?id=98355#c29">Comment # 29</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [SNB 4.8] gpu at 0x7955b000, but request was 0x77b0b000" href="https://bugs.freedesktop.org/show_bug.cgi?id=98355">bug 98355</a> from <a class="email" href="mailto:mariusz.libera@gmail.com" title="Mariusz Libera <mariusz.libera@gmail.com>"> Mariusz Libera</a> <pre>Created <a href="attachment.cgi?id=127767" name="attach_127767" title="cat /sys/class/drm/card0/error | bzip2 > error.bz2">attachment 127767</a> <a href="attachment.cgi?id=127767&action=edit" title="cat /sys/class/drm/card0/error | bzip2 > error.bz2">[details]</a> cat /sys/class/drm/card0/error | bzip2 > error.bz2 Another hang: [ 1842.449017] [drm] GPU HANG: ecode 6:0:0x87e8effd, in chrome [1452], reason: Hang on render ring, action: reset [ 1842.449019] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 1842.449020] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 1842.449020] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 1842.449021] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 1842.449022] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 1842.449079] drm/i915: Resetting chip after gpu hang</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>