|Summary:||Filing "GPU HANG" Bug (as requested by dmesg)|
|Component:||DRM/Intel||Assignee:||Intel GFX Bugs mailing list <intel-gfx-bugs>|
|Status:||RESOLVED MOVED||QA Contact:||Intel GFX Bugs mailing list <intel-gfx-bugs>|
|i915 platform:||CFL||i915 features:||GPU hang|
Description mailhol.vincent 2019-10-20 17:35:59 UTC
Created attachment 145779 [details] results of 'cat /sys/class/drm/card0/error > error', 'dmesg > dmesg' and 'uname -a' > uname I saw below text in dmesg, so as requested, I am filing a bug report. >> GPU HANG: ecode 9:2:0xfffffffe, in systemd-logind , hang on bcs0 >> GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel drm/i915 developers can then reassign to the right component if it's not a kernel issue. The gpu crash dump is required to analyze gpu hangs, so please always attach it. GPU crash dump saved to /sys/class/drm/card0/error I saw no symptoms aside of the dmesg report. On the user side everything seems OK. So far, this is a single occurrence. As you can see in dmesg log, please also note that the kernel was "tainted" because I loaded a network module (no public release of that module available).
Comment 1 Chris Wilson 2019-10-20 18:18:43 UTC
Huh, an unterminated batch buffer. GPU overran into the wrong batch and exploded.
Comment 2 Martin Peres 2019-11-29 19:42:28 UTC
-- 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/drm/intel/issues/532.