Bug 112073 - Filing "GPU HANG" Bug (as requested by dmesg)
Summary: Filing "GPU HANG" Bug (as requested by dmesg)
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: lowest not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-20 17:35 UTC by mailhol.vincent
Modified: 2019-10-21 06:19 UTC (History)
1 user (show)

See Also:
i915 platform: CFL
i915 features: GPU hang


Attachments
results of 'cat /sys/class/drm/card0/error > error', 'dmesg > dmesg' and 'uname -a' > uname (50.48 KB, application/x-xz)
2019-10-20 17:35 UTC, mailhol.vincent
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
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 [301], 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.


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.