Created attachment 122689 [details] /sys/class/drm/card0/error I just had a graphics lockup ( which thankfully was recoverable ). dmesg had instructions to enter a bug here ... [19457.321443] [drm] stuck on render ring [19457.324988] [drm] GPU HANG: ecode 9:0:0x85dffffb, in chrome [30231], reason: Ring hung, action: reset [19457.325006] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [19457.325013] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [19457.325020] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [19457.325027] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [19457.325034] [drm] GPU crash dump saved to /sys/class/drm/card0/error [19457.328502] drm/i915: Resetting chip after gpu hang [19457.328654] [drm:i915_gem_init_hw [i915]] *ERROR* Failed to initialize GuC, error -5 (ignored) [19459.321864] [drm] RC6 on [22771.424833] [drm] stuck on render ring [22771.426978] [drm] GPU HANG: ecode 9:0:0x85dffffb, in chrome [31399], reason: Ring hung, action: reset [22771.429866] drm/i915: Resetting chip after gpu hang [22771.429996] [drm:i915_gem_init_hw [i915]] *ERROR* Failed to initialize GuC, error -5 (ignored) [22773.416859] [drm] RC6 on [22777.428986] [drm] stuck on render ring [22777.430703] [drm] GPU HANG: ecode 9:0:0x85dffffb, in chrome [31399], reason: Ring hung, action: reset [22777.433190] drm/i915: Resetting chip after gpu hang [22777.433346] [drm:i915_gem_init_hw [i915]] *ERROR* Failed to initialize GuC, error -5 (ignored) [22779.425753] [drm] RC6 on I'm using: x11-drivers/xf86-video-intel-2.99.917_p20160213 media-libs/mesa-11.1.2-r1 x11-base/xorg-server-1.17.4 sys-kernel/linux-sabayon-4.4.6 I've attached the GPU hang from /sys/class/drm/card0/error as instructed. Let me know if there is anything else I can do.
For both bugs: - Hung happening on "render" ring, - Application is "Chrome", - HW/PCI_ID is "0x1916" - Instruction/IPETH is "0x7a000004" *** This bug has been marked as a duplicate of bug 92934 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.