Created attachment 141658 [details] GPU Crash Dump I encountered the mentioned error message several times now today. It seems to be occurring just now, probably after a system upgrade which is done automatically in my case (Using Fedora Workstation 27). I attached the output from the latest GPU crash dump (/sys/class/drm/card0/error) as advised in the journalctl entry: Sep 20 14:09:39 henry-workstation /usr/libexec/gdm-x-session[1923]: i965: Failed to submit batchbuffer: Input/output error Sep 20 14:09:39 henry-workstation kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Sep 20 14:09:31 henry-workstation kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Sep 20 14:09:23 henry-workstation kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Sep 20 14:09:15 henry-workstation kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Sep 20 14:09:07 henry-workstation kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Sep 20 14:09:07 henry-workstation kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error Sep 20 14:09:07 henry-workstation kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Sep 20 14:09:07 henry-workstation kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Sep 20 14:09:07 henry-workstation kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Sep 20 14:09:07 henry-workstation kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Sep 20 14:09:07 henry-workstation kernel: [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1925], reason: hang on rcs0, action: reset
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1759.
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.