<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - drm i915 "GPU HANG" in kernel-4.19.7 on starting X" href="https://bugs.freedesktop.org/show_bug.cgi?id=108966#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - drm i915 "GPU HANG" in kernel-4.19.7 on starting X" href="https://bugs.freedesktop.org/show_bug.cgi?id=108966">bug 108966</a> from <a class="email" href="mailto:wjfgb@mypostoffice.co.uk" title="William <wjfgb@mypostoffice.co.uk>"> William</a> <pre>It does seem to be a very very rare happening. Since my initial bug report I have had only one similar happening in May 2019 under kernel-5.0.15, again soon after startup, but I did not notice it at the time, and so failed to get a GPU crash dump, the /var/log/messages showed :- May 15 18:46:35 localhost kernel: [drm] GPU HANG: ecode 5:0:0x005f5f5f, in Xorg [796], reason: hang on rcs0, action: reset May 15 18:46:35 localhost kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. May 15 18:46:35 localhost kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel May 15 18:46:35 localhost kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. May 15 18:46:35 localhost kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. May 15 18:46:35 localhost kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error May 15 18:46:35 localhost kernel: i915 0000:00:02.0: Resetting chip for hang on rcs0 It has not happened again since and is more of a curiosity than a problem so if you wish to close the bug that is ok.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>