<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [skl] Kwin crashing"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101885#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [skl] Kwin crashing"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101885">bug 101885</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>Looking at the backtrace it looks like there is some sort of of clean-up going
on, destructor for KWin::SceneOpenGL::Texture getting called. What surprises me
a bit is that it seems to kick off rendering with GPU as
isl_emit_depth_stencil_hiz_s() gets called to setup the hardware.
For normal rendering there is its own path for setting depth+stencil and ending
up here means that the GPU is being setup for blorp.
Anyway, is ~Texture() really suppose to render something and more importantly
is the driver context still suppose to be valid at this point. Looking at:
6 0x00007f294cfdb534 in isl_gen5_emit_depth_stencil_hiz_s (dev=0x0,
batch=0x1344830, info=0x1) at
/var/tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/intel/isl/isl_emit_depth_stencil.c:67
All three arguments are pointers and must be valid, first is simply NULL and
third clearly invalid "0x1".</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>