[Bug 88626] New: [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jan 20 04:10:50 PST 2015


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

            Bug ID: 88626
           Summary: [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking
                    stuck semaphore on render ring, action: continue
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: samuel.rakitnican at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

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

[ 2649.511762] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck
semaphore on render ring, action: continue
[ 2649.511765] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 2649.511766] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 2649.511766] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 2649.511767] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 2649.511768] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 5434.461348] SELinux: initialized (dev tmpfs, type tmpfs), uses transition
SIDs
[ 8183.284486] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck
semaphore on render ring, action: continue
[ 8427.230201] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck
semaphore on render ring, action: continue
[ 9034.572822] SELinux: initialized (dev tmpfs, type tmpfs), uses transition
SIDs

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


More information about the intel-gfx-bugs mailing list