[Bug 112073] New: Filing "GPU HANG" Bug (as requested by dmesg)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=112073

            Bug ID: 112073
           Summary: Filing "GPU HANG" Bug (as requested by dmesg)
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: not set
          Priority: not set
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: mailhol.vincent at wanadoo.fr
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 145779
  --> https://bugs.freedesktop.org/attachment.cgi?id=145779&action=edit
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).

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20191020/2f4d2651/attachment.html>