<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 --- - [Bisected]igt/gem_concurrent_blit/cpu-early-read-forked fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68830">68830</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>daniel@ffwll.ch
</td>
</tr>
<tr>
<th>Summary</th>
<td>[Bisected]igt/gem_concurrent_blit/cpu-early-read-forked fails
</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=85036" name="attach_85036" title="dmesg">attachment 85036</a> <a href="attachment.cgi?id=85036&action=edit" title="dmesg">[details]</a></span>
dmesg
System Environment:
--------------------------
Platform: PNV/ILK/SNB/IVB/HSW
Kernel: (drm-intel-nightly)4508e539b642ff40ad57f3ab7721ed2862da2eb5
Bug detailed description:
-----------------------------
It fails on PNV/ILK/SNB/IVB/HSW.It happens on drm-intel-nightly,
drm-intel-next-queued, drm-intel-fixes kernel.
Following cases also fail:
igt/gem_concurrent_blit/cpu-gpu-read-after-write-forked
igt/gem_concurrent_blit/cpu-overwrite-source-forked
igt/gem_concurrent_blit/gtt-early-read-forked
igt/gem_concurrent_blit/gtt-gpu-read-after-write-forked
igt/gem_concurrent_blit/gtt-overwrite-source-forked
igt/gem_concurrent_blit/prw-early-read-forked
igt/gem_concurrent_blit/prw-gpu-read-after-write-forked
igt/gem_concurrent_blit/prw-overwrite-source-forked
Bisect shows:cd1f220847c34610ab9e07c3cf1c5a7e77284eb8 is the first bad commit
commit cd1f220847c34610ab9e07c3cf1c5a7e77284eb8
Author: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
AuthorDate: Thu Aug 29 10:06:51 2013 +0200
Commit: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
CommitDate: Thu Aug 29 18:18:33 2013 +0200
lib/drmtest: extract igt_fork from gem_concurrent_blt
Making sure that we correctly collect the exit codes from all children
is a bit a hassle. So add another magic igt codeblock for easy forking
and joining.
Note that children are (currently at least) not allowed to call igt_skip.
Add an assert to enforce this.
v2:
- Properly propagate the exit code.
- Fix the segfault.
- Add a child int and num_children paramter to the magic codeblock as
suggested by Chris Wilson.
- Don't dump noise into stdout when a child thread fails, the parent
will do that for us already.
v3: Now with some docs.
v4: Fixup igt_waitchildren to properly reset state so it can be used
again.
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
output:
Subtest cpu-early-read-forked: FAIL
Reproduce steps:
----------------------------
1. ./gem_concurrent_blit --run-subtest cpu-early-read-forked</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>
</ul>
</body>
</html>