<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 6:1:0xffeffffe, in multiqueue1:src [12807], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=91657#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 6:1:0xffeffffe, in multiqueue1:src [12807], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=91657">bug 91657</a> from <a class="email" href="mailto:linux@eikelenboom.it" title="Sander Eikelenboom <linux@eikelenboom.it>"> Sander Eikelenboom</a> <pre>On 2015-10-30 05:51, <a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a> wrote: > <a class="bz_bug_link bz_status_NEW " title="NEW - [drm] GPU HANG: ecode 6:1:0xffeffffe, in multiqueue1:src [12807], reason: Ring hung, action: reset" href="show_bug.cgi?id=91657">https://bugs.freedesktop.org/show_bug.cgi?id=91657</a> > > --- <a href="show_bug.cgi?id=91657#c1">Comment #1</a> from haihao <<a href="mailto:haihao.xiang@intel.com">haihao.xiang@intel.com</a>> --- > Sorry for slow response, could you provide the link you accessed in > firefox ? Hi, It seems to happen in about every movie, but just tested again f.e. the movie in: <a href="https://tweakers.net/video/11055/lara-reist-de-wereld-af-in-launchtrailer-rise-of-the-tomb-raider.html">https://tweakers.net/video/11055/lara-reist-de-wereld-af-in-launchtrailer-rise-of-the-tomb-raider.html</a> It seems to (only) happen when you skip back and forth through the movie while playing it, but after the crash it doesn't recover and you only get a green screen (with sound). The crash seemed a little bit different this time so here it is: [ 786.874201] [drm] stuck on render ring [ 786.879854] [drm] GPU HANG: ecode 6:0:0x87e8effd, in MediaPl~back #3 [5143], reason: Ring hung, action: reset [ 786.890811] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 786.901184] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 786.911135] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 786.915040] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 786.917068] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 786.921628] drm/i915: Resetting chip after gpu hang [ 792.872050] [drm] stuck on render ring [ 792.877512] [drm] GPU HANG: ecode 6:0:0x87e8effd, in MediaPl~back #5 [5354], reason: Ring hung, action: reset [ 792.888571] [drm:i915_set_reset_status] *ERROR* gpu hanging too fast, banning! [ 792.898954] drm/i915: Resetting chip after gpu hang GPU crash dump is also attached. Kernel in the meantime is 4.3-rc7 Debian Jessie va-api package versions installed are: ii gstreamer1.0-vaapi:amd64 0.5.9-2 amd64 VA-API plugins for GStreamer ii gstreamer1.0-vaapi-doc 0.5.9-2 all GStreamer VA-API documentation and manuals ii libgstreamer-vaapi1.0-0:amd64 0.5.9-2 amd64 GStreamer libraries from the "vaapi" set ii libgstreamer-vaapi1.0-dev 0.5.9-2 amd64 GStreamer development files for libraries from the "vaapi" set ii i965-va-driver:amd64 1.4.1-2 amd64 VAAPI driver for Intel G45 & HD Graphics family ii libva-dev:amd64 1.4.1-1 amd64 Video Acceleration (VA) API for Linux -- development files ii libva-drm1:amd64 1.4.1-1 amd64 Video Acceleration (VA) API for Linux -- DRM runtime ii libva-egl1:amd64 1.4.1-1 amd64 Video Acceleration (VA) API for Linux -- EGL runtime ii libva-glx1:amd64 1.4.1-1 amd64 Video Acceleration (VA) API for Linux -- GLX runtime ii libva-tpi1:amd64 1.4.1-1 amd64 Video Acceleration (VA) API for Linux -- TPI runtime ii libva-wayland1:amd64 1.4.1-1 amd64 Video Acceleration (VA) API for Linux -- Wayland runtime ii libva-x11-1:amd64 1.4.1-1 amd64 Video Acceleration (VA) API for Linux -- X11 runtime ii libva1:amd64 1.4.1-1 amd64 Video Acceleration (VA) API for Linux -- runtime</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>