[Bug 101482] New: GPU HANG: ecode 9:0:0x86dffffd, in chrome [2055], reason: Hang on render ring, action: reset

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 101482
           Summary: GPU HANG: ecode 9:0:0x86dffffd, in chrome [2055],
                    reason: Hang on render ring, 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: trilader+bugs-fdo at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 132022
  --> https://bugs.freedesktop.org/attachment.cgi?id=132022&action=edit
Crash Log

CPU: Xeon E3-1245v5
Kernel: 4.11.3
Mesa: 17.1.2-1
X11: 1.19.3-2
Distribution: Arch Linux


49297.455466] [drm] GPU HANG: ecode 9:0:0x86dffffd, in chrome [2055], reason:
Hang on render ring, action: reset
[49297.455468] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[49297.455468] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[49297.455468] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[49297.455468] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[49297.455469] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[49297.455512] drm/i915: Resetting chip after gpu hang
[49297.455615] [drm] RC6 on
[49297.471708] [drm] GuC firmware load skipped
[49305.341832] drm/i915: Resetting chip after gpu hang
[49305.341933] [drm] RC6 on
[49305.361937] [drm] GuC firmware load skipped
[49315.368699] drm/i915: Resetting chip after gpu hang
[49315.368783] [drm] RC6 on
[49315.384170] [drm] GuC firmware load skipped

-- 
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/20170617/e3594995/attachment.html>