[Bug 88727] New: [drm] GPU HANG ecode 0:0x00ababab, in systemd-logind [248], reason: Ring hung, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jan 22 18:05:16 PST 2015


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

            Bug ID: 88727
           Summary: [drm] GPU HANG ecode 0:0x00ababab, in systemd-logind
                    [248], reason: Ring hung, action: reset
           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: cache.1024mb at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 112696
  --> https://bugs.freedesktop.org/attachment.cgi?id=112696&action=edit
Error log

I actually didn't know what happen, but as I open dmesg it shows this, so I
just submit this.

System is Archlinux 64-bit, Kernel 3.18 (as shown in the error log).

The dmesg tells 2 error, but only produce 1 error log, for a reason I just
don't know. Quoting dmesg:

[182837.319770] [drm] GPU HANG: ecode 0:0x00ababab, in systemd-logind [248],
reason: Ring hung, action: reset
[182837.319772] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[182837.319774] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[182837.319775] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[182837.319776] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[182837.319777] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[183084.318376] [drm] stuck on render ring
[183084.319809] [drm] GPU HANG: ecode 0:0x003d3d3d, in systemd-logind [248],
reason: Ring hung, action: reset

-- 
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/20150123/d71b837d/attachment.html>


More information about the intel-gfx-bugs mailing list