Created attachment 129438 [details] GPU crash dump mhw ~ # uname -m x86_64 mhw ~ # uname -r 4.4.39-gentoo Gentoo Linux on Dell 9020-AIO, internal display connection to integrated panel. Logged kernel messages: Feb 9 08:18:39 mhw kernel: [drm] GPU HANG: ecode 7:0:0xeed3ffff, reason: Ring hung, action: reset Feb 9 08:18:39 mhw kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Feb 9 08:18:39 mhw kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Feb 9 08:18:39 mhw kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Feb 9 08:18:39 mhw kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Feb 9 08:18:39 mhw kernel: [drm] GPU crash dump saved to /sys/class/drm/card1/error Feb 9 08:18:39 mhw kernel: drm/i915: Resetting chip after gpu hang This happened several minutes after logon. I didn't notice at the time and don't know what was being done then. The adjacent log entries are minutes away in both directions.
It was running slowly, but it shouldn't have declared that as a hang. commit 3fe3b030bd2d7a51c12aa6fe0e5178b9f1a726ec Author: Mika Kuoppala <mika.kuoppala@linux.intel.com> Date: Fri Nov 18 15:09:04 2016 +0200 drm/i915: Decouple hang detection from hangcheck period
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.