[Bug 93645] New: GPU HANG: ecode 9:0:0x84df7efc, in java [1628], reason: Ring hung, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Jan 9 02:13:03 PST 2016


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

            Bug ID: 93645
           Summary: GPU HANG: ecode 9:0:0x84df7efc, in java [1628],
                    reason: Ring hung, action: reset
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: lokedhs at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 120918
  --> https://bugs.freedesktop.org/attachment.cgi?id=120918&action=edit
GPU crash dump from /sys/class/drm/card0/error

While playing Minecraft, I am getting the following error in dmesg:

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

-- 
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/20160109/7b328886/attachment.html>


More information about the intel-gfx-bugs mailing list