Hi, Reporting bug as requested. The /sys/class/drm/card0/error is empty, however. [701284.032117] [drm] stuck on render ring [701284.032562] [drm] GPU HANG: ecode 7:0:0x85ffbff8, in chromium [21515], reason: Ring hung, action: reset [701284.032563] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [701284.032564] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [701284.032564] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [701284.032565] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [701284.032566] [drm] GPU crash dump saved to /sys/class/drm/card0/error [701284.034662] drm/i915: Resetting chip after gpu hang [701290.032349] [drm] stuck on render ring [701290.032795] [drm] GPU HANG: ecode 7:0:0x85ffbff8, reason: Ring hung, action: reset [701290.035673] drm/i915: Resetting chip after gpu hang
Is it still reproducible ? If this is still the case please attached corresponding /sys/class/drm/card0/error and also try v4.6-rc5 or later.
There's no evidence of this issue in my machine's journalctl log which contains data starting from 10-Apr.
Closing as non reproducible.
Created attachment 132007 [details] This is the gpu crash dump as saved to /sys/class/drm/card0/error. [drm] stuck on render ring
Comment on attachment 132007 [details] This is the gpu crash dump as saved to /sys/class/drm/card0/error. Sorry, it isn't not a error log, it is the gpu crash dump. :-)
Created attachment 132008 [details] The dmesg, if needed. [drm] Initialized i915 1.6.0 20080730
Created attachment 132009 [details] Last -and least the Xorg.0.log (EE) intel(0): Detected a hung GPU, disabling acceleration.
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.