<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bug] LibVA h.264 capture/encoding causes Weston to hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=69330#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bug] LibVA h.264 capture/encoding causes Weston to hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=69330">bug 69330</a> from <a class="email" href="mailto:ullysses.a.eoff@intel.com" title="U. Artie Eoff <ullysses.a.eoff@intel.com>"> U. Artie Eoff</a> <pre>(In reply to <a href="show_bug.cgi?id=69330#c4">comment #4</a>) > Why is the experimental - proof of concept - Weston screen capture > problem/bug being assigned to libva? Well, that's the first I've heard about it being a experimental POC. Nonetheless, it's a bug and can be further triaged as you see fit. LibVA h.264 capture is about to be released as a feature in Weston. IRCC, using the feature causes a GPU hang too, only on Sandybridge, and likely rules out Weston itself. So libva or the libva intel-driver seems like the next logical component to investigate/assign until evidence shows otherwise. Who knows, maybe it's a kernel-level bug like some of the decode hangs we've encountered (Brian did rule out RC6)?? > Can Ander look at it first and triage? > Or is this not using the proof of concept screen capture program from Ander? Yeh, seems like a logical [co-]owner since Ander enabled the feature in Weston. Not sure if there is another "vehicle" (apart from Weston) to test the libva h.264 encoding pipeline. If there is, then that might be a good place to look at the bug.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>