[Bug 93505] New: GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [4626], reason: Ring hung, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Dec 25 10:00:44 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=93505
Bug ID: 93505
Summary: GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [4626],
reason: Ring hung, action: reset
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: francois at fmarier.org
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 120686
--> https://bugs.freedesktop.org/attachment.cgi?id=120686&action=edit
GPU crash dump from /sys/class/drm/card0/error
I just noticed this in my logs:
[drm] stuck on render ring
[drm] GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [4626], reason: Ring hung,
action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack,
including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI ->
DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's
not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always
attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
drm/i915: Resetting chip after gpu hang
The crash dump is attached.
-- chipset: Sandybridge Mobile
-- system architecture: amd64
-- xf86-video-intel: xserver-xorg-video-intel 2:2.99.917-2
-- xserver: xserver-xorg-core 2:1.17.3-2
-- mesa: libegl1-mesa 11.0.8-1
-- libdrm: libdrm-intel1 2.4.65-3
-- kernel: 4.3.0-1
-- Linux distribution: Debian Sid
-- Machine or mobo model: Lenovo ThinkPad T420
-- Display connector: internal
--
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/20151225/568ace0c/attachment.html>
More information about the intel-gfx-bugs
mailing list