<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [HSW] GPU HANG: ecode 7:0:0x85dffffc, in chrome [3388], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=97252#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [HSW] GPU HANG: ecode 7:0:0x85dffffc, in chrome [3388], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=97252">bug 97252</a> from <a class="email" href="mailto:bzb@poczta.onet.pl" title="Zbigniew Czapiga <bzb@poczta.onet.pl>"> Zbigniew Czapiga</a> <pre>Hi Mark, Yes, I was using xf86-video-intel, but I tried modesetting as well: 1. I added modesetting to /etc/X11/xorg.conf Section "Device" Identifier "Intel Graphics" Driver "modesetting" 2. xrandr --list-providers confirmed that I was using modesetting: Providers: number : 1 Provider 0: id: 0x45 cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 3 associated providers: 0 name:modesetting 3. glxinfo showed DRI3 LIBGL_DEBUG=verbose glxinfo | grep libgl libGL: Using DRI3 for screen 0 Unfortunatelly after some time driver crashed: [Fri Dec 9 15:35:54 2016] [drm] stuck on render ring [Fri Dec 9 15:35:54 2016] [drm] GPU HANG: ecode 7:0:0x85dffcfc, in chrome [1877], reason: Ring hung, action: reset [Fri Dec 9 15:35:54 2016] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [Fri Dec 9 15:35:54 2016] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [Fri Dec 9 15:35:54 2016] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [Fri Dec 9 15:35:54 2016] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [Fri Dec 9 15:35:54 2016] [drm] GPU crash dump saved to /sys/class/drm/card0/error</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>