[Mesa-dev] [Bug 105049] Invalid usage of vulkan pipeline barriers can cause amdgpu to deadlock

[bugzilla-daemon at freedesktop.org]

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

--- Comment #7 from Samuel Pitoiset <samuel.pitoiset at gmail.com> ---
Well, the validation layers report a bunch of errors with your app, like:

Validation layer: (F8)  [ VUID-vkCmdEndRenderPass-commandBuffer-cmdpool ]
Object: 0x5638b8e4f6b0 (Type = 6) | Cannot call vkCmdEndRenderPass() on a
command buffer allocated from a pool without VK_QUEUE_GRAPHICS_BIT
capabilities.. The Vulkan spec states: The VkCommandPool that commandBuffer was
allocated from must support graphics operations
(https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkCmdEndRenderPass-commandBuffer-cmdpool)

Validation layer: (F8)  [
UNASSIGNED-CoreValidation-DrawState-InvalidImageLayout ] Object: 0x5638b8279a80
(Type = 6) | Submitted command buffer expects image 0x3 (subresource:
aspectMask 0x1 array layer 0, mip level 0) to be in layout
VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL--instead, image 0x3's current layout
is VK_IMAGE_LAYOUT_UNDEFINED.

Validation layer: (F8)  [ VUID-vkCmdBeginRenderPass-commandBuffer-cmdpool ]
Object: 0x5638b8e5a3f0 (Type = 6) | Cannot call vkCmdBeginRenderPass() on a
command buffer allocated from a pool without VK_QUEUE_GRAPHICS_BIT
capabilities.. The Vulkan spec states: The VkCommandPool that commandBuffer was
allocated from must support graphics operations
(https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkCmdBeginRenderPass-commandBuffer-cmdpool)

As Vulkan is a low-level API, it's not surprising that the GPU hangs if you do
something bad. The first step is to *always* enable the validation layers in
order to make sure your application is correct. If after fixing all errors the
GPU still hangs with RADV, it might be a problem in the driver.

Feel free to re-open if the problem still happens after making sure you use the
API the right way.

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20181218/372c86a9/attachment-0001.html>