<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [HSW Regression] intel_do_flush_locked failed: Invalid argument"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91844">91844</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[HSW Regression] intel_do_flush_locked failed: Invalid argument
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>andreas.reis@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=118041" name="attach_118041" title="dmesg (2015y-09m-01d-10h-47m-22s), 4200U started with drm.debug=7">attachment 118041</a> <a href="attachment.cgi?id=118041&action=edit" title="dmesg (2015y-09m-01d-10h-47m-22s), 4200U started with drm.debug=7">[details]</a></span>
dmesg (2015y-09m-01d-10h-47m-22s), 4200U started with drm.debug=7
Getting said failure since a few days on 4200U and 4770, currently on
drm-intel-nightly: 2015y-09m-01d-10h-47m-22s. mesa, libdrm etc. are git
versions from today as well.
Basically any program (other than the first after boot, which always seems to
succeed) trying to use certain hardware acceleration has a high chance of
failing. It isn't consistent though, sometimes the programs run in later tries
just to fail again in yet further ones afterwards.
Specifically, I've seen it happen with Chrome, Steam and every mesa-demo I've
tried.
grepping the attacked dmesg for i915 yields in repetition:
[drm:i915_gem_open]
[drm:i915_gem_context_create_ioctl] HW context 1 created
[drm:i915_parse_cmds] CMD: Command length exceeds batch length: 0x092C51B8
length=58 batchlen=22
[drm:i915_parse_cmds] CMD: batch set OACONTROL but did not clear it</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>