<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>high
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - igt/gem_evict_everything/forked-interruptible causes <3>[ 172.855126] [drm:i915_set_reset_status] *ERROR* blitter ring hung inside bo (0x60690000 ctx 0) at 0x60690020"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71374">71374</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>igt/gem_evict_everything/forked-interruptible causes <3>[ 172.855126] [drm:i915_set_reset_status] *ERROR* blitter ring hung inside bo (0x60690000 ctx 0) at 0x60690020
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>huax.lu@intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</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=88872" name="attach_88872" title="dmesg">attachment 88872</a> <a href="attachment.cgi?id=88872&action=edit" title="dmesg">[details]</a></span>
dmesg
System Environment:
--------------------------
Platform: Pineview/GM45/Ironlake/Sandybridge/Ivybridge/Haswell/Baytrail
Kernel: (drm-intel-nightly)2f29640dfa2e434361a834fb40c89eedd66cb235
Bug detailed description:
-------------------------
It fails on all platforms with -fixes, -nightly and -queued kernel.
Following cases also have this issue:
igt/gem_evict_everything/forked-mempressure-interruptible
igt/gem_evict_everything/forked-mempressure-normal
igt/gem_evict_everything/forked-multifd-interruptible
igt/gem_evict_everything/forked-multifd-mempressure-interruptible
igt/gem_evict_everything/forked-multifd-mempressure-normal
igt/gem_evict_everything/forked-multifd-normal
igt/gem_evict_everything/forked-normal
igt/gem_evict_everything/forked-swapping-interruptible
igt/gem_evict_everything/forked-swapping-mempressure-interruptible
igt/gem_evict_everything/forked-swapping-mempressure-normal
igt/gem_evict_everything/forked-swapping-multifd-interruptible
igt/gem_evict_everything/forked-swapping-multifd-mempressure-interruptible
igt/gem_evict_everything/forked-swapping-multifd-mempressure-normal
igt/gem_evict_everything/forked-swapping-multifd-normal
igt/gem_evict_everything/forked-swapping-normal
igt/gem_evict_everything/major-interruptible
igt/gem_evict_everything/major-normal
igt/gem_evict_everything/minor-interruptible
igt/gem_evict_everything/minor-normal
igt/gem_evict_everything/swapping-interruptible
igt/gem_evict_alignment/major-interruptible
igt/gem_evict_alignment/major-normal
igt/gem_evict_alignment/minor-interruptible
igt/gem_evict_alignment/minor-normal
igt/gem_linear_blits/interruptible
igt/gem_linear_blits/normal
Bisect shows:
f4dfa37e8578419b94a7c84fbcea7d4b70aa68b9 is the first bad commit
commit f4dfa37e8578419b94a7c84fbcea7d4b70aa68b9
Author: Ben Widawsky <<a href="mailto:benjamin.widawsky@intel.com">benjamin.widawsky@intel.com</a>>
AuthorDate: Tue Oct 8 15:02:07 2013 -0700
Commit: Ben Widawsky <<a href="mailto:benjamin.widawsky@intel.com">benjamin.widawsky@intel.com</a>>
CommitDate: Wed Nov 6 09:34:35 2013 -0800
bdw: Update obvious missing blit support
This provides a macro that allows us to update all the arbitrary blit
commands we have stuck throughout the code. It assumes we don't actually
use 64b relocs (which is currently true). This also allows us to easily
find
all the areas we need to update later when we really use the upper dword.
This block was done mostly with a sed job, and represents the easier
in test blit implementations.
v2 by Oscar: s/OUT_BATCH/BEGIN_BATCH in BLIT_COPY_BATCH_START
CC: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Signed-off-by: Ben Widawsky <<a href="mailto:ben@bwidawsk.net">ben@bwidawsk.net</a>>
Signed-off-by: Oscar Mateo <<a href="mailto:oscar.mateo@intel.com">oscar.mateo@intel.com</a>>
output:
Subtest forked-interruptible: SUCCESS
Reproduce steps:
-------------------------
1. ./gem_evict_everything --run-subtest forked-interruptible</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>