[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-06-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 Danylo changed: What|Removed |Added CC||danylo.pilia...@gmail.com Resolution|-

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-06-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 Denis changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #12 from Denis --- Jason

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-04-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #11 from alge...@tuta.io --- I believe I'm running into a related (or the same) error: Arch Linux with an AMD RX580 GPU Mesa 19.0.2-1 vulkan-radeon 19.0.2-1 libxcb 1.13.1-1 xorg-server 1.20.4-1 vulkan-tools 1.1.102-1 Process 3567 (v

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-04-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #10 from Jason Ekstrand --- Unfortunately, thanks fo Vulkan passing everything as struct pointers, a backtrack with `bt full` isn't as useful as one would like. That said, given where it's crashing, I'm 93% sure that both of those b

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-04-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #9 from Denis --- bt all didn't provide anything, so I did same with Kenneth. Output below: (gdb) bt all No symbol "all" in current context. (gdb) thread apply all backtrace Thread 2 (Thread 0x76c37700 (LWP 11457)): #0 0x

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-04-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 Denis changed: What|Removed |Added CC||denys.kos...@globallogic.co |

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-04-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #8 from Denis --- >/build/vulkan-tools/src/Vulkan-Tools-1.1.102/vulkaninfo/vulkaninfo.c:4504: >failed with VK_ERROR_OUT_OF_HOST_MEMORY Actually that's exactly what I got in "normal" version. I discussed this error with dev and he s

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-04-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #7 from Kenneth Endfinger --- Oddly enough, with vulkan-tools 1.1.102: /build/vulkan-tools/src/Vulkan-Tools-1.1.102/vulkaninfo/vulkaninfo.c:4504: failed with VK_ERROR_OUT_OF_HOST_MEMORY is now the error... -- You are receiving th

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-04-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #6 from Kenneth Endfinger --- Is this what you are looking for? (gdb) thread apply all backtrace Thread 2 (Thread 0x738f8700 (LWP 8010)): #0 0x77ba7afc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-04-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #5 from Jason Ekstrand --- Can you reproduce with a full debug build in gdb and run "bt all"? -- You are receiving this mail because: You are the assignee for the bug.___ mesa-dev mailing

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-04-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #4 from Denis --- looks like I made a bisect for this issue. Jason, could you please take a look to it? It shows your commit. [manjaro@manjaro-pc mesa]$ git bisect good 68df93ecbcee6215ac49e0c6f62ae818d2bc9962 is the first bad co

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-03-29 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #3 from Denis --- hi, I am able to reproduce this issue on Manjaro OS and intel (CFL CPU), with system (18.3.4) and built from git mesa versions. Can I provide some additional information for you to help in debugging? Core was gene

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-03-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 --- Comment #2 from Kenneth Endfinger --- I am also running an AMD eGPU over ThunderBolt: Section "Device" Identifier "AMD" Driver "amdgpu" BusID "PCI:61:0:0" Option "AllowEmptyInitialConfiguration" Option "AllowExternalGpus" EndSecti

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-03-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 Samuel Pitoiset changed: What|Removed |Added CC||airl...@freedesktop.org,

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-03-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 Kenneth Endfinger changed: What|Removed |Added Hardware|x86 (IA32) |x86-64 (AMD64) -- You are receivin

[Mesa-dev] [Bug 110261] Segmentation fault when using vulkaninfo on Radeon

2019-03-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110261 Bug ID: 110261 Summary: Segmentation fault when using vulkaninfo on Radeon Product: Mesa Version: 19.0 Hardware: x86 (IA32) OS: Linux (All) Status: NEW S