[Bug 89334] New: 4.0-rc1 kernel GPU hang: ecode 3:0:0x02faffcf (i915) stuck on render ring ecode 3:0:0x02faffcf
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Feb 26 00:05:08 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=89334
Bug ID: 89334
Summary: 4.0-rc1 kernel GPU hang: ecode 3:0:0x02faffcf (i915)
stuck on render ring ecode 3:0:0x02faffcf
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: jimmcdevitt60 at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
After eliminating the other members of the stack, It appears that 4.0~rc1 has a
regression. One of two things happen:
1)
Feb 25 18:24:42 Aesop kernel: [ 1318.339897] [drm] stuck on render ring
Feb 25 18:24:42 Aesop kernel: [ 1318.341695] [drm] GPU HANG: ecode
3:0:0x02e6ffc1, in Xorg [2282], reason: Ring hung, action: reset
Feb 25 18:24:42 Aesop kernel: [ 1318.341698] [drm] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Feb 25 18:24:42 Aesop kernel: [ 1318.341700] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Feb 25 18:24:42 Aesop kernel: [ 1318.341702] [drm] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Feb 25 18:24:42 Aesop kernel: [ 1318.341703] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
Feb 25 18:24:42 Aesop kernel: [ 1318.341705] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Feb 25 18:24:42 Aesop kernel: [ 1318.371624] drm/i915: Resetting chip after gpu
hang
Feb 25 18:48:56 Aesop kernel: [ 2772.339749] [drm] stuck on render ring
Feb 25 18:48:56 Aesop kernel: [ 2772.341710] [drm] GPU HANG: ecode
3:0:0x02faffcf, in Xorg [2282], reason: Ring hung, action: reset
Feb 25 18:48:56 Aesop kernel: [ 2772.371456] drm/i915: Resetting chip after gpu
hang
which you can restart X (provided you know your system blind as nothing is
intelligent on the screen.) This occurs seemingly at random, frequently.
2)
The system just locks - screen perfectly frozen. Cycle the power. No trace of
any crash or oops.
As usual, for item one - you can not get at the crash dump when you try to ssh
into the box to look at it; its ALWAYS empty (/sys/class/drm/card0/error). Also
there is no pattern as to when it happens either.
Additional info:
OpenGL renderer string: Gallium 0.4 on i915 (chipset: 945G)
OpenGL version string: 2.1 Mesa 10.4.5
Compiled with: gcc version 4.9.2 (Both OS & Mesa)
xorg-server: 1.15.1
Module intel: vendor="X.Org Foundation"
compiled for 1.15.1, module version = 2.99.917
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 15.0
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.0.0-0-reaper
root=UUID=8536097e-c02a-4a8c-9cdf-b40ba4e3b74d ro
crashkernel=384M-2G:64M,2G-:128M
drm_kms_helper.edid_firmware=edid/1280x1024_75.bin thermal.crt=75 quiet splash
vt.handoff=7
BIOS DMI: ECS 945GCT-M2/945GCT-M2, BIOS 080012 07/18/2008
Thanks in advance again for your help.
--
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/20150226/20f9023c/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list