<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BDW] [Bisected] Absolute constant buffers break VAAPI in mpv"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102774#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [BDW] [Bisected] Absolute constant buffers break VAAPI in mpv"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102774">bug 102774</a>
from <span class="vcard"><a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> <span class="fn">Kenneth Graunke</span></a>
</span></b>
<pre>So, trying with Mesa 17.1 on Kabylake...mpv renders black with a theora video,
GPU hangs immediately with a VC1 video, and with H264, renders garbage colors
and/or black and GPU hangs. The GPU hangs are definitely a vaapi batch, not
from Mesa.
I don't think this is a Mesa bug. It seems like there are a lot of bugs in
vaapi. And the setting my patch changed is definitely supposed to be
per-context, so Mesa changing it shouldn't affect vaapi at all. vaapi probably
doesn't use contexts explicitly, but I thought the kernel was supposed to give
every process a context by default, to prevent state leaks like this.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>