[Bug 90329] New: kernel: [drm] GPU HANG: ecode 8:0:0xfffffffe, in chromium [26167], reason: Ring hung, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue May 5 15:29:28 PDT 2015


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

            Bug ID: 90329
           Summary: kernel: [drm] GPU HANG: ecode 8:0:0xfffffffe, in
                    chromium [26167], reason: Ring hung, action: reset
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: sadieperkins at riseup.net
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

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

3 seconds after resume from suspend, chromium's "/usr/lib/chromium/chromium
--type=gpu-process" process was using 100% cpu and had to be killed:



kernel: [drm] stuck on render ring
kernel: [drm] GPU HANG: ecode 8:0:0xfffffffe, in chromium [26167], reason: Ring
hung, action: reset
kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack,
including userspace.
kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against
DRI -> DRM/Intel
kernel: [drm] drm/i915 developers can then reassign to the right component if
it's not a kernel issue.
kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please
always attach it.
kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
kernel: drm/i915: Resetting chip after gpu hang

-- 
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/20150505/1049d0ce/attachment-0001.html>


More information about the intel-gfx-bugs mailing list