[Bug 93470] New: GPU HANG: ecode 7:0:0x85dfbff8, in chrome [2700], reason: Ring hung, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Dec 21 10:35:30 PST 2015


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

            Bug ID: 93470
           Summary: GPU HANG: ecode 7:0:0x85dfbff8, in chrome [2700],
                    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: hkskoglund at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 120629
  --> https://bugs.freedesktop.org/attachment.cgi?id=120629&action=edit
cat /sys/class/drm/card0/error +dmesg + journal + xrandr

After resume from sleep I got GPU Hang on fedora rawhide in chrome. I don't
know how to reproduce the issue, but it seems like its related to suspend (it
has occured several times before after resume from suspend).

des. 21 19:12:02 satellite kernel: [drm] GPU HANG: ecode 7:0:0x85dfbff8, in
chrome [2700], reason: Ring hung, action: reset
des. 21 19:12:02 satellite kernel: [drm] GPU hangs can indicate a bug anywhere
in the entire gfx stack, including userspace.
des. 21 19:12:02 satellite kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
des. 21 19:12:02 satellite kernel: [drm] drm/i915 developers can then reassign
to the right component if it's not a kernel issue.
des. 21 19:12:02 satellite kernel: [drm] The gpu crash dump is required to
analyze gpu hangs, so please always attach it.
des. 21 19:12:02 satellite kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
des. 21 19:12:02 satellite kernel: drm/i915: Resetting chip after gpu hang
des. 21 19:12:02 satellite google-chrome.desktop[2599]:
[2700:2700:1221/191202:ERROR:gles2_cmd_decoder.cc(12198)] Onscreen context lost
via ARB/EXT_robustness. Reset status = GL_GUILTY_CONTEXT_RESET_KHR
des. 21 19:12:02 satellite google-chrome.desktop[2599]:
[2700:2700:1221/191202:ERROR:gles2_cmd_decoder.cc(3581)]   GLES2DecoderImpl:
Context reset detected after MakeCurrent.
des. 21 19:12:02 satellite google-chrome.desktop[2599]:
[2700:2700:1221/191202:ERROR:gpu_command_buffer_stub.cc(1186)] Exiting GPU
process because some drivers cannot recover from problems.
des. 21 19:12:02 satellite google-chrome.desktop[2599]:
[2599:2599:1221/191202:ERROR:gpu_process_transport_factory.cc(621)] Lost UI
shared context.

-- 
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/20151221/6d32de4d/attachment.html>


More information about the intel-gfx-bugs mailing list