[Bug 99157] New: [drm] stuck on render ring, drm/i915 - report requested

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Dec 20 11:14:15 UTC 2016


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

            Bug ID: 99157
           Summary: [drm] stuck on render ring, drm/i915 - report
                    requested
           Product: DRI
           Version: unspecified
          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: thomas.schorpp at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

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

Dec 19 17:23:25 tom3 kernel: [5217537.820042] [drm] stuck on render ring
Dec 19 17:23:25 tom3 kernel: [5217537.821077] [drm] GPU HANG: ecode
0:0x8644f8fe, in chromium [6523], reason: Ring hung, action: reset
Dec 19 17:23:25 tom3 kernel: [5217537.821079] [drm] GPU hangs can indicate a
bug anywhere in the entire gfx stack, including userspace.
Dec 19 17:23:25 tom3 kernel: [5217537.821081] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Dec 19 17:23:25 tom3 kernel: [5217537.821083] [drm] drm/i915 developers can
then reassign to the right component if it's not a kernel issue.
Dec 19 17:23:25 tom3 kernel: [5217537.821084] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
Dec 19 17:23:25 tom3 kernel: [5217537.821086] [drm] GPU crash dump saved to
/sys/class/drm/card0/error

-- 
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/20161220/792a11ff/attachment.html>


More information about the intel-gfx-bugs mailing list