[Bug 102940] Regression: Vulkan KMS rendering crashes since 17.2

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=102940

            Bug ID: 102940
           Summary: Regression: Vulkan KMS rendering crashes since 17.2
           Product: Mesa
           Version: 17.2
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Vulkan/intel
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: lubosz at gmail.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org
                CC: jason at jlekstrand.net

Created attachment 134422
  --> https://bugs.freedesktop.org/attachment.cgi?id=134422&action=edit
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.
https://github.com/krh/vkcube
https://github.com/vkmark/vkmark

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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20170922/77c201ce/attachment.html>