So AFAIU this is a framework right? Any demo apps using it that reproduce the issue?

On Mon, Jun 3, 2019, 12:53 AM <bugzilla-daemon@freedesktop.org> wrote:
Bug ID 110815
Summary Segfault vkCreateDescriptorPool in The-Forge on RADV
Product Mesa
Version git
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component Drivers/Vulkan/radeon
Assignee mesa-dev@lists.freedesktop.org
Reporter boberfly@gmail.com
QA Contact mesa-dev@lists.freedesktop.org

Hello,

I am using the oibaf mesa-vulkan-drivers which I believe is the latest git
(just updated to 30th May 2019 build here 19.2~git1906010730.755906~oibaf~b
running Linux Kernel 5.0.2 on Ubuntu 18.04). I have recently got segfaults when
running vkCreateDescriptorPool with The-Forge which has worked perfectly before
in the past on multiple OSes/Vulkan implementations, including RADV:
https://github.com/ConfettiFX/The-Forge
I maintain a 'lite' edition so it is easier for me to embed into other
projects, which is probably easier to test with:
https://github.com/boberfly/The-Forge-Lite

I narrowed it down to this line crashing in the RADV vulkan driver when running
the 01_Transformations example:
https://github.com/boberfly/The-Forge-Lite/blob/v1.27/src/Renderer/Vulkan/Vulkan.cpp#L477
From:
https://github.com/boberfly/The-Forge-Lite/blob/v1.27/src/Examples/01_Transformations/01_Transformations.cpp#L226

The error I get is pretty vague:
[1185298.570160] MainThread[39052]: segfault at c ip 00007fe119abd604 sp
00007ffc01e6afc8 error 4 in libvulkan_radeon.so[7fe11992b000+230000]
[1185298.570179] Code: 24 18 85 d2 41 89 94 24 00 02 00 00 0f 84 37 01 00 00 48
8d 44 24 10 45 31 f6 31 ed 45 31 ed 31 db 48 89 04 24 90 49 8b 57 18 <4a> 8b 34
32 43 89 5c 74 0c 8b 4e 04 4b 89 34 74 85 c9 74 2e 83 e9

I can only say that roughly a month ago this was running fine on an older RADV
version. I am using the latest Vulkan 1.1.106 SDK from LunarG as well.

Hardware: HP z620 w/ 2x Xeon E5-2680v2, AMD Radeon Vega Frontier Edition 16GB

I hope I have enough information here to explain the issue.


You are receiving this mail because:
  • You are the assignee for the bug.
  • You are the QA Contact for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev