<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW] GPU HANG: ecode 7:0:0x86dfbff9, in Xorg [376], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=98976#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW] GPU HANG: ecode 7:0:0x86dfbff9, in Xorg [376], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=98976">bug 98976</a> from <a class="email" href="mailto:boiteamadmax@hotmail.com" title="Matthieu <boiteamadmax@hotmail.com>"> Matthieu</a> <pre>I've the same trouble on an up-to-date Debian Testing x64 running on an Intel(R) Core(TM) i3-2125 CPU's GPU. I've notice this bug since less than a week. Here is the dmesg: [ 8598.205058] [drm] GPU HANG: ecode 6:0:0xc2fffffc, in Xorg [729], reason: Hang on render ring, action: reset [ 8598.205060] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 8598.205060] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 8598.205060] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 8598.205060] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 8598.205061] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 8598.205099] drm/i915: Resetting chip after gpu hang And I've attached the error file as asked. No specific action, maybe webpage changing on Vivaldi. uname -a Linux Cube 4.8.0-1-amd64 #1 SMP Debian 4.8.7-1 (2016-11-13) x86_64 GNU/Linux</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> </ul> </body> </html>