[Bug 106931] New: GPU HANG: ecode 9:0:0x85dffffb, in electron [21270], reason: Ring hung, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jun 15 21:47:23 UTC 2018


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

            Bug ID: 106931
           Summary: GPU HANG: ecode 9:0:0x85dffffb, in electron [21270],
                    reason: Ring hung, action: reset
           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: melmacjim at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 140177
  --> https://bugs.freedesktop.org/attachment.cgi?id=140177&action=edit
The attached file is the output from /sys/class/drm/card0/error

Sorry if this is more noise on top of 102397 and 102470 (both a chrome and
chromium), but I found this similar issue in the dmesg output :

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

This was the very last dmesg entry and grepping for "\[drm\]" only resulted in
the same output.

$ dmesg -T |grep "\[drm\]"
[Tue Jun 12 19:31:46 2018] [drm] stuck on render ring
[Tue Jun 12 19:31:46 2018] [drm] GPU HANG: ecode 9:0:0x85dffffb, in electron
[21270], reason: Ring hung, action: reset
[Tue Jun 12 19:31:46 2018] [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
[Tue Jun 12 19:31:46 2018] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[Tue Jun 12 19:31:46 2018] [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
[Tue Jun 12 19:31:46 2018] [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
[Tue Jun 12 19:31:46 2018] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
[Tue Jun 12 19:31:48 2018] [drm] RC6 on

Also, I've attached the /sys/class/drm/card0/error log (named
sys_class_drm_card0_error_20180618).

Thanks.

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


More information about the intel-gfx-bugs mailing list