<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 --- - [BDW]igt/gem_persistent_relocs/forked-faulting-reloc-thrash-inactive causes assertion failure function"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72103">72103</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>[BDW]igt/gem_persistent_relocs/forked-faulting-reloc-thrash-inactive causes assertion failure function
</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>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jinxianx.guo@intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</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=89944" name="attach_89944" title="dmesg">attachment 89944</a> <a href="attachment.cgi?id=89944&action=edit" title="dmesg">[details]</a></span>
dmesg
System Environment:
--------------------------
Platform: Broadwell
kernel (drm-intel-nexe-queued)8b4f49e03901e82898540bd1189333edf9588d74
Some additional commit info:
Author: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>>
Date: Mon Nov 25 15:51:16 2013 -0800
drm/i915: split fb allocation and initialization v2
If we use a stolen buffer, our probe callback shouldn't allocate a new
buffer; we should re-use the one from the BIOS instead if possible.
v2: fix locking (Jesse)
Bug detailed description:
-----------------------------
Assertion failure shown while run the case.
This is the first time to run igt test on Broadwell.
Following cases also have this issue.
igt/gem_persistent_relocs/forked-faulting-reloc-thrashing
igt/gem_persistent_relocs/forked-interruptible-faulting-reloc
igt/gem_persistent_relocs/forked-interruptible-faulting-reloc-thrash-inactive
igt/gem_persistent_relocs/forked-interruptible-faulting-reloc-thrashing
igt/gem_persistent_relocs/forked-interruptible-thrash-inactive
igt/gem_persistent_relocs/forked-interruptible-thrashing
igt/gem_persistent_relocs/forked-thrash-inactive
igt/gem_persistent_relocs/forked-thrashing
Error log:
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Test assertion failure function gem_execbuf, file drmtest.c:556:
Test assertion failure function gem_execbuf, file drmtest.c:556:
Failed assertion: ret == 0
Failed assertion: ret == 0
child 0 failed with exit status 99
Subtest forked-faulting-reloc-thrash-inactive: FAIL
gem_persistent_relocs: drmtest.c:1181: children_exit_handler: Assertion
`kill(test_children[nc], 3) == 0' failed.
Aborted (core dumped)
Steps:
---------------------------
./gem_persistent_relocs --run-subtest forked-faulting-reloc-thrash-inactive</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>