[Bug 97004] New: Stuck on render ring error GPU hang

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jul 20 11:17:58 UTC 2016


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

            Bug ID: 97004
           Summary: Stuck on render ring error GPU hang
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: graeme at hinchliffesolutions.co.uk
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

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

Lost input from USB keyboard to open processes, USB mouse still continued to
move pointer.

kern.log contained:

Jul 20 11:25:49 PN-DEV-52 kernel: [10705.960637] [drm] stuck on render ring
Jul 20 11:25:49 PN-DEV-52 kernel: [10705.960641] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Jul 20 11:25:49 PN-DEV-52 kernel: [10705.960642] [drm] GPU hangs can indicate a
bug anywhere in the entire gfx stack, including userspace.
Jul 20 11:25:49 PN-DEV-52 kernel: [10705.960642] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Jul 20 11:25:49 PN-DEV-52 kernel: [10705.960643] [drm] drm/i915 developers can
then reassign to the right component if it's not a kernel issue.
Jul 20 11:25:49 PN-DEV-52 kernel: [10705.960644] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.


As per instructions opening new bug and attaching crash dump

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


More information about the intel-gfx-bugs mailing list