[Bug 93056] New: i915 Ring hung gpu hang
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Nov 21 08:02:50 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=93056
Bug ID: 93056
Summary: i915 Ring hung gpu hang
Product: DRI
Version: DRI git
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: lists.jjorge at free.fr
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 120005
--> https://bugs.freedesktop.org/attachment.cgi?id=120005&action=edit
cat /sys/class/drm/card0/error
[ 31.385362] [drm] Initialized drm 1.1.0 20060810
[ 31.797907] [drm] Memory usable by graphics device = 128M
[ 31.797923] fb: switching to inteldrmfb from VESA VGA
[ 31.798760] [drm] Replacing VGA console driver
[ 31.801404] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 31.801411] [drm] Driver supports precise vblank timestamp query.
[ 31.822545] [drm] initialized overlay support
[ 31.823395] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor
0
[ 31.894944] fbcon: inteldrmfb (fb0) is primary device
[ 31.895817] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 83.704043] [drm] stuck on render ring
[ 83.743458] [drm] GPU HANG: ecode 2:0:0x540fffc7, in X [844], reason: Ring
hung, action: reset
[ 83.743468] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 83.743471] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 83.743473] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 83.743475] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 83.743477] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 83.747972] drm/i915: Resetting chip after gpu hang
[ 83.748020] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -19
--
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/20151121/1a7fa392/attachment.html>
More information about the intel-gfx-bugs
mailing list