[Bug 91082] Crash/Fail when calling glFenceSync

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Sep 12 13:06:26 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=91082

Eero Tamminen <eero.t.tamminen at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #3 from Eero Tamminen <eero.t.tamminen at intel.com> ---
(In reply to Damian Dixon from comment #0)
> The following is reported on the console:
> 
> intel_do_flush_locked failed: No such file or directory

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 comment #1)
> 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.

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 comment #2)
> 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)?

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?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160912/88b34b97/attachment.html>


More information about the intel-3d-bugs mailing list