<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - 4.0-rc1 kernel GPU hang: ecode 3:0:0x02faffcf (i915) stuck on render ring ecode 3:0:0x02faffcf"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89334">89334</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>4.0-rc1 kernel GPU hang: ecode 3:0:0x02faffcf (i915) stuck on render ring ecode 3:0:0x02faffcf
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jimmcdevitt60@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>