Created attachment 134294 [details] except from /var/log/syslog & Xorg.0.log.old Sep 17 15:42:55 figini kernel: [21119.663759] [drm] GPU HANG: ecode 9:1:0xeeffefa1, in Xorg [975], reason: Hang on bcs0, action: reset Sep 17 15:42:55 figini kernel: [21119.663763] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Sep 17 15:42:55 figini kernel: [21119.663765] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Sep 17 15:42:55 figini kernel: [21119.663766] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Sep 17 15:42:55 figini kernel: [21119.663767] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Sep 17 15:42:55 figini kernel: [21119.663769] [drm] GPU crash dump saved to /sys/class/drm/card0/error Sep 17 15:42:55 figini kernel: [21119.664027] drm/i915: Resetting chip after gpu hang Sep 17 15:42:55 figini kernel: [21119.666159] BUG: unable to handle kernel NULL pointer dereference at 0000000000000070 Sep 17 15:42:55 figini kernel: [21119.666266] IP: reset_common_ring+0x9a/0x100 [i915] Sep 17 15:42:55 figini kernel: [21119.666293] PGD 171d40067 Sep 17 15:42:55 figini kernel: [21119.666294] P4D 171d40067 Sep 17 15:42:55 figini kernel: [21119.666309] PUD 175d67067 Sep 17 15:42:55 figini kernel: [21119.666357] PMD 0 Sep 17 15:42:55 figini kernel: [21119.666374] Sep 17 15:42:55 figini kernel: [21119.666399] Oops: 0000 [#1] SMP
typo in attachment description. I meant excerpt (not except).
It is unusual for the hw to die that badly (resulting in an oops) without us having first screwed up some of the state tracking. But fwiw, we have just landed a different method for recovering from a catastrophic GPU hang on drm-tip [https://cgit.freedesktop.org/drm-tip]
This has been already added some time ago as: https://bugs.freedesktop.org/show_bug.cgi?id=102393
*** This bug has been marked as a duplicate of bug 102393 ***
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.