<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [SKL bisected] texsubimage pbo intermittent failures"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91926#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [SKL bisected] texsubimage pbo intermittent failures"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91926">bug 91926</a>
from <span class="vcard"><a class="email" href="mailto:topi.pohjolainen@intel.com" title="Topi Pohjolainen <topi.pohjolainen@intel.com>"> <span class="fn">Topi Pohjolainen</span></a>
</span></b>
<pre>This is another random observation. I noticed that _mesa_meta_pbo_TexSubImage()
itself stores the current gl-state and resets the state for new meta operation
(calls _mesa_meta_begin()). This is followed by a call
_mesa_meta_BlitFramebuffer() which in turn does the same - stores the current
gl-state and resets it again (by calling _mesa_meta_begin() also). This should
be fine as the meta-state mechanism is designed for nested operations.
This is just used quite rarely and therefore possible (though unlikely) source
for a lurking bug.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>