<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Regression: Vulkan KMS rendering crashes since 17.2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102940">102940</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Regression: Vulkan KMS rendering crashes since 17.2
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>17.2
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/Vulkan/intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>lubosz@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>jason@jlekstrand.net
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=134422" name="attach_134422" title="master: vkcube on Braswell">attachment 134422</a> <a href="attachment.cgi?id=134422&action=edit" title="master: vkcube on Braswell">[details]</a></span>
master: vkcube on Braswell
Vulkan KMS rendering breaks with commit
818b8579145196c7a8d4095bd5e65367e02a8fef
I could reproduce the crash on Haswell, Braswell and Skylake with vkcube and
vkmark.
<a href="https://github.com/krh/vkcube">https://github.com/krh/vkcube</a>
<a href="https://github.com/vkmark/vkmark">https://github.com/vkmark/vkmark</a>
kmscube still works, the issue is limited to Vulkan.
I produced backtraces at the following commits, which are different.
818b8579145196c7a8d4095bd5e65367e02a8fef First bad
d6d2b6b5ec9b1638c0827582872670c7da79bb53 17.2.1
df8767a14e3eae4dcb8241b731b34e9379706795 Master
On some platforms in some commits stash smashing is detected:
*** stack smashing detected ***: <unknown> terminated
vkmark does not always crash, look for SIGINT in the backtraces where it just
froze.
Crash overview:
| First bad | 17.2.1 | Master
_____________________________________________________________________________________
vkcube | anv_CreateImageView | anv_CreateImageView | vk_alloc
vkmark | isl_surf_fill_state_s | isl_surf_fill_state_s |
anv_image_fill_surface_state</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>