[Bug 103381] New: GPU hang, Kicking stuck wait on rcs0

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 103381
           Summary: GPU hang, Kicking stuck wait on rcs0
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: fkyleung at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 134954
  --> https://bugs.freedesktop.org/attachment.cgi?id=134954&action=edit
GPU crash dump

Following crash report instructions in dmesg. This was encountered during a
play session of Starbound through Steam. Working with a Xeon E3 1275 V6.

[78854.543221] [drm] GPU HANG: ecode 9:-1:0x00000000, reason: Kicking stuck
wait on rcs0, action: continue
[78854.543222] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[78854.543222] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[78854.543223] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[78854.543223] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[78854.543224] [drm] GPU crash dump saved to /sys/class/drm/card1/error
[78858.379785] asynchronous wait on fence i915:gnome-shell[26449]/1:2b3d0 timed
out

-- 
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/20171021/b459f2c5/attachment.html>