[Bug 81578] New: intel_do_flush_locked when trying to use clEnqueueAcquireGLObjects

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Jul 20 16:17:35 PDT 2014


          Priority: medium
            Bug ID: 81578
          Assignee: idr at freedesktop.org
           Summary: intel_do_flush_locked when trying to use
        QA Contact: intel-3d-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: wallnuss13 at gmail.com
          Hardware: Other
            Status: NEW
           Version: 10.2
         Component: Drivers/DRI/i965
           Product: Mesa

I posted this bug on the (user) mailing list without getting any answers.
Orignal posting:
http://lists.freedesktop.org/archives/mesa-users/2014-June/000837.html and

The gist of what I am trying to do is:

after creating the correct OpenCL and OpenGL contexts and the Texture and Image
object I want to do the following calls to copy the computed information from
the OpenCL Buffer to the Image.


After clEnqueueAcquireGLObjects I get the following error:
"intel_do_flush_locked failed: No such file or directory"

The command itself succeeds but if I put a breakpoint on it and step through
the rest of the function I get that error right after the call.

The problem might stem from my setup. I am using the AMD OpenCL implementation
on an Intel CPU in combination with mesa on an Intel HD3000.

On the other hand if I use llvmpipe it works fine and I also don't get an error
when running it with INTEL_NO_HW=1

Since I am new to mesa debugging how would I go about to get you more usable
information? In the Github repo linked above I have a small c test case for the
scenario I am describing and which reproduces the problem on two different
laptops reliably.

Best Valentin

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

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