[Bug 90833] New: GPU HANG: ecode 4:0:0x8644f8fe, in chrome [12486], reason: Ring hung, action: rese
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Jun 3 13:49:43 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90833
Bug ID: 90833
Summary: GPU HANG: ecode 4:0:0x8644f8fe, in chrome [12486],
reason: Ring hung, action: rese
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: sultbab at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 116271
--> https://bugs.freedesktop.org/attachment.cgi?id=116271&action=edit
/sys/class/drm/card0/error
[13001.000054] [drm] stuck on render ring
[13001.001025] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [12486], reason:
Ring hung, action: reset
[13001.001028] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[13001.001030] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[13001.001031] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[13001.001033] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[13001.001035] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[13001.252277] drm/i915: Resetting chip after gpu hang
[13016.000105] [drm] stuck on render ring
[13016.001081] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [12486], reason:
Ring hung, action: reset
[13016.028115] drm/i915: Resetting chip after gpu hang
[13021.988127] [drm] stuck on render ring
[13021.989076] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [12486], reason:
Ring hung, action: reset
[13022.016069] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast,
banning!
[13022.016147] drm/i915: Resetting chip after gpu hang
[13036.000124] [drm] stuck on render ring
[13036.001073] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [13631], reason:
Ring hung, action: reset
[13036.032122] drm/i915: Resetting chip after gpu hang
[13041.988129] [drm] stuck on render ring
[13041.989118] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [13631], reason:
Ring hung, action: reset
[13042.020095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast,
banning!
[13042.020177] drm/i915: Resetting chip after gpu hang
[13047.988115] [drm] stuck on render ring
[13047.989089] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [13652], reason:
Ring hung, action: reset
[13048.020177] drm/i915: Resetting chip after gpu hang
[13054.000052] [drm] stuck on render ring
[13054.001020] [drm] GPU HANG: ecode 4:0:0x8644f8fe, in chrome [13652], reason:
Ring hung, action: reset
[13054.028086] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast,
banning!
[13054.028164] drm/i915: Resetting chip after gpu hang
--
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/20150603/57424f66/attachment.html>
More information about the intel-gfx-bugs
mailing list