<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Crash/Fail when calling glFenceSync"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91082">bug 91082</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>NEEDINFO
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Crash/Fail when calling glFenceSync"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91082#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Crash/Fail when calling glFenceSync"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91082">bug 91082</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Damian Dixon from <a href="show_bug.cgi?id=91082#c0">comment #0</a>)
<span class="quote">> The following is reported on the console:
>
> intel_do_flush_locked failed: No such file or directory</span >
I.e. flushing batch failed and libdrm returned error from kernel ioctl().
"No such file or directory" means that user-space gave kernel an invalid
handle.
To find out what exactly is the problem, you need to add "drm.debug=0xe" to
kernel command line and provide "dmesg" output after the problem.
(In reply to Damian Dixon from <a href="show_bug.cgi?id=91082#c1">comment #1</a>)
<span class="quote">> Further testing has shown that this problem occurs when I have multiple
> OpenGL contexts in different threads.
>
> This approach works on Windows 7/8.1 and on Linux with AMD and NVIDIA
> drivers. It also works on Windows 8.1 with the intel drivers.</span >
My first guess would be that something in your program had already closed the
handle when glFenceSync() was called.
On which Intel HW this happened?
(In reply to Kenneth Graunke from <a href="show_bug.cgi?id=91082#c2">comment #2</a>)
<span class="quote">> Mesa 10.2 is pretty ancient - the 10.2 series is originally from June 2014.
> The last bug fixes to that branch were in September 2014.
>
> Could you try with Mesa 10.6 (the most recent release)?</span >
Some time has passed since, Mesa 11.2 is now common in distros. Could test
that, or later, or provide minimized version of your use-case for testing?</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>