<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Intel driver fails with "intel_do_flush_locked failed: No such file or directory" if buffer imported with EGL_NATIVE_PIXMAP_KHR" href="https://bugs.freedesktop.org/show_bug.cgi?id=71759#c42">Comment # 42</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Intel driver fails with "intel_do_flush_locked failed: No such file or directory" if buffer imported with EGL_NATIVE_PIXMAP_KHR" href="https://bugs.freedesktop.org/show_bug.cgi?id=71759">bug 71759</a> from <a class="email" href="mailto:hojuruku@gmail.com" title="Luke McKee <hojuruku@gmail.com>"> Luke McKee</a> <pre>As for the discussion about this defect not existing having trouble to replicate... I'm a gentoo user. The Mesa 12.0.1 ebuild has this defect. "intel_do_flush_locked failed: No such file or directory", and system call trace showed some kind of locking error before totem borked. To resolve this issue I used the <a href="https://bugs.freedesktop.org/attachment.cgi?id=125508">https://bugs.freedesktop.org/attachment.cgi?id=125508</a> i965: import prime buffers in the current context, not screen patch from intel and now totem works using va-api acceleration. Only mesa was rebuilt with the patch to resolve this issue. This is the hardware I am running. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz stepping : 3 microcode : 0x19 00:02.0 0300: 8086:0412 (rev 06) (prog-if 00 [VGA controller]) Subsystem: 1462:7850 Flags: bus master, fast devsel, latency 0, IRQ 24 Memory at f7800000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 If you need any more information on my setup to assist in replicating the defect let me know.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>