<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 --- - [HSW Regression]igt/gem_exec_bad_domains/conflicting-write-domain fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78645">78645</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>[HSW Regression]igt/gem_exec_bad_domains/conflicting-write-domain fails
</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>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=98955" name="attach_98955" title="dmesg">attachment 98955</a> <a href="attachment.cgi?id=98955&action=edit" title="dmesg">[details]</a></span>
dmesg
==System Environment==
--------------------------
Regression: Yes.
But I didn't find out good commit on -next-queued branch
Non-working platforms: HSW
==kernel==
--------------------------
-nightly: ed60c2747e0be176f28dc3dadba564949d90d821 (fails)
-queued: 1cf0ba14740d96fbf6f58a201f000a34b74f4725 (fails)
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Mon May 5 09:07:33 2014 +0100
drm/i915: Flush request queue when waiting for ring space
During the review of
commit 1f70999f9052f5a1b0ce1a55aff3808f2ec9fe42
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Mon Jan 27 22:43:07 2014 +0000
drm/i915: Prevent recursion by retiring requests when the ring is full
Ville raised the point that our interaction with request->tail was
likely to foul up other uses elsewhere (such as hang check comparing
ACTHD against requests).
However, we also need to restore the implicit retire requests that certain
test cases depend upon (e.g. igt/gem_exec_lut_handle), this raises the
spectre that the ppgtt will randomly call i915_gpu_idle() and recurse
back into intel_ring_begin().
Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Bugzilla: <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [PNV/HSW/BDW bisected]igt/gem_exec_lut_handle is slow"
href="show_bug.cgi?id=78023">https://bugs.freedesktop.org/show_bug.cgi?id=78023</a>
Reviewed-by: Brad Volkin <<a href="mailto:bradley.d.volkin@intel.com">bradley.d.volkin@intel.com</a>>
[danvet: Remove now unused 'tail' variable as spotted by Brad.]
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
-fixes: 05adaf1f101f25f40f12c29403e6488f0e45f6b6 (works)
Author: Jani Nikula <<a href="mailto:jani.nikula@intel.com">jani.nikula@intel.com</a>>
Date: Fri May 9 14:52:34 2014 +0300
drm/i915/vlv: reset VLV media force wake request register
Media force wake get hangs the machine when the system is booted without
displays attached. The assumption is that (at least some versions of)
the firmware has skipped some initialization in that case.
Empirical evidence suggests we need to reset the media force wake
request register in addition to the render one to avoid hangs.
Bugzilla: <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [BYT] Media forcewake timeout with no displays connected"
href="show_bug.cgi?id=75895">https://bugs.freedesktop.org/show_bug.cgi?id=75895</a>
Reported-by: Imre Deak <<a href="mailto:imre.deak@intel.com">imre.deak@intel.com</a>>
Reported-by: Darren Hart <<a href="mailto:dvhart@linux.intel.com">dvhart@linux.intel.com</a>>
Tested-by: Darren Hart <<a href="mailto:dvhart@linux.intel.com">dvhart@linux.intel.com</a>>
Reviewed-by: Mika Kuoppala <<a href="mailto:mika.kuoppala@intel.com">mika.kuoppala@intel.com</a>>
Cc: <a href="mailto:stable@vger.kernel.org">stable@vger.kernel.org</a>
Signed-off-by: Jani Nikula <<a href="mailto:jani.nikula@intel.com">jani.nikula@intel.com</a>>
==Bug detailed description==
-----------------------------
igt/gem_exec_bad_domains/conflicting-write-domain fails
Output:
./gem_exec_bad_domains --run-subtest conflicting-write-domain
IGT-Version: 1.6-gd848a36 (x86_64) (Linux:
3.15.0-rc3_drm-intel-next-queued_1cf0ba_20140512+ x86_64)
Test assertion failure function __real_main153, file
gem_exec_bad_domains.c:204:
Last errno: 22, Invalid argument
Failed assertion: run_batch() == 0
Subtest conflicting-write-domain: FAIL
==Reproduce steps==
----------------------------
1. ./gem_exec_bad_domains --run-subtest conflicting-write-domain</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>