[Bug 104440] New: GPU HANG: ecode 9:0:0x84df1cfc, in stanley_linux [1772], reason: Hang on rcs0, action: reset

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 104440
           Summary: GPU HANG: ecode 9:0:0x84df1cfc, in stanley_linux
                    [1772], reason: Hang on rcs0, action: reset
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: freedesktop-bugs at jbeekman.nl
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

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

This happens every time in the same location in the game (Stanley Parable)

jan 01 14:18:20 jethro kernel: [drm] GPU HANG: ecode 9:0:0x84df1cfc, in
stanley_linux [1772], reason: Hang on rcs0, action: reset
jan 01 14:18:20 jethro kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack, including userspace.
jan 01 14:18:20 jethro kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
jan 01 14:18:20 jethro kernel: [drm] drm/i915 developers can then reassign to
the right component if it's not a kernel issue.
jan 01 14:18:20 jethro kernel: [drm] The gpu crash dump is required to analyze
gpu hangs, so please always attach it.
jan 01 14:18:20 jethro kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
jan 01 14:18:20 jethro kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang

-- 
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/20180101/ba672732/attachment.html>