<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [drm] stuck on render ring with Linux 3.15.5, works with 3.14.11"
href="https://bugs.freedesktop.org/show_bug.cgi?id=81369">81369</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[drm] stuck on render ring with Linux 3.15.5, works with 3.14.11
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>freedesktop.flibble@mandarb.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg CVS
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=102812" name="attach_102812" title="Crash dump">attachment 102812</a> <a href="attachment.cgi?id=102812&action=edit" title="Crash dump">[details]</a></span>
Crash dump
Jul 14 21:04:59 balrog kernel: [ 293.552750] [drm] stuck on render ring
Jul 14 21:04:59 balrog kernel: [ 293.553208] [drm] GPU HANG: ecode
0:0x85fffff8, in Xorg [14516], reason: Ring hung, action: reset
Jul 14 21:04:59 balrog kernel: [ 293.553210] [drm] GPU hangs can indicate a
bug anywhere in the entire gfx stack, including userspace.
Jul 14 21:04:59 balrog kernel: [ 293.553211] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Jul 14 21:04:59 balrog kernel: [ 293.553212] [drm] drm/i915 developers can
then reassign to the right component if it's not a kernel issue.
Jul 14 21:04:59 balrog kernel: [ 293.553213] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
Jul 14 21:04:59 balrog kernel: [ 293.553214] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Jul 14 21:05:01 balrog kernel: [ 295.551577] [drm] Enabling RC6 states: RC6
on, RC6p off, RC6pp off
Jul 14 21:05:05 balrog kernel: [ 299.553243] [drm] stuck on blitter ring
Jul 14 21:05:05 balrog kernel: [ 299.553717] [drm] GPU HANG: ecode
2:0xfffffffe, in Xorg [14516], reason: Ring hung, action: reset
Jul 14 21:05:05 balrog kernel: [ 299.553760] [drm:i915_context_is_banned]
*ERROR* gpu hanging too fast, banning!
Jul 14 21:05:07 balrog kernel: [ 301.552531] [drm] Enabling RC6 states: RC6
on, RC6p off, RC6pp off
To me, this looks pretty similar to bug <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [3.15 regression] relocation value wraparound due to bios-fb preserved hole at 0"
href="show_bug.cgi?id=78533">Bug 78533</a>, except the two patches do
not apply cleanly to my 3.15.5 kernel:
1 > cat ../patches/Prevent\ negative\ relocation\ deltas\ from\ causing\
wraparound.patch | patch -l -s -p1 --dry-run
3 out of 4 hunks FAILED
1 > cat ../patches/Offsect\ batch\ buffers\ to\ prevent\ delta\ wrapping.patch
| patch -l -s -p1 --dry-run
2 out of 2 hunks FAILED
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
5 out of 5 hunks ignored
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
2 out of 2 hunks ignored
5 out of 6 hunks FAILED
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
1 out of 1 hunk ignored</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>