<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [BYT, HSW, SKL, BXT, KBL] GPU hangs with GfxBench 4.0 CarChase"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96743#c47">Comment # 47</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [BYT, HSW, SKL, BXT, KBL] GPU hangs with GfxBench 4.0 CarChase"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96743">bug 96743</a>
from <span class="vcard"><a class="email" href="mailto:topi.pohjolainen@intel.com" title="Topi Pohjolainen <topi.pohjolainen@intel.com>"> <span class="fn">Topi Pohjolainen</span></a>
</span></b>
<pre>(In reply to Topi Pohjolainen from <a href="show_bug.cgi?id=96743#c45">comment #45</a>)
<span class="quote">> Dumping batches seems to change the runtime dynamics too much and the hang
> just won't reoccur. I even tried a more light-weight version of batch
> dumping which just checks that instruction is valid. Both require mapping
> and un-mapping of the underlying buffer object which might prevent/hide the
> hang from reappearing within reasonable amount time.</span >
Checking instructions before flushing allows one to read the batch thru the
mapping used for batch emission. With that I was actually able to catch the
user space writing an invalid instruction. Checking that now.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>