[Bug 112085] New: i915 GPU HANG: ecode 6:1:0xfffffffe, in PapersPlease [21853], hang on rcs0

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 112085
           Summary: i915 GPU HANG: ecode 6:1:0xfffffffe, in PapersPlease
                    [21853], hang on rcs0
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: not set
          Priority: not set
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: naoliv at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 145789
  --> https://bugs.freedesktop.org/attachment.cgi?id=145789&action=edit
/sys/class/drm/card0/error output

I was playing Papers Please while the GPU hang.

In dmesg I have:

[101677.029941] i915 0000:00:02.0: GPU HANG: ecode 6:1:0xfffffffe, in
PapersPlease [21853], hang on rcs0
[101677.029943] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[101677.029944] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[101677.029944] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[101677.029945] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[101677.029946] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[101677.030105] i915 0000:00:02.0: Resetting chip for hang on rcs0

/sys/class/drm/card0/error output is attached.

Linux is:
Linux spades 5.3.0-trunk-amd64 #1 SMP Debian 5.3.2-1~exp1 (2019-10-02) x86_64
GNU/Linux

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