https://bugs.freedesktop.org/show_bug.cgi?id=105119
Bug ID: 105119
Summary: Desktop-wide input freeze when vulkan (radv)
Product: Mesa
Version: 17.3
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Vulkan/radeon
Assignee: mesa-dev@lists.freedesktop.org
Reporter: ja...@okonski.org
QA Contact: mesa-dev@lists.freedesktop.org
Created attachment 137384
--> https://bugs.freedesktop.org/attachment.cgi?id=137384&action=edit
trace #1 with long vkDeviceWaitIdle
I'm experimenting with vulkan, and, after my application exits cleanly,
keyboard input is ignored until I switch to another window using my mouse (that
I can still use).
This is not the main problem though, I found a sequence of commands that
triggers a desktop-wide freeze. I can still move my mouse, but windows don't
redraw as far as I can tell. I also cannot focus other windows with
mouse/keyboard, I cannot use ctrl+alt+f[1-9] to jump back to tty. Because I
have a physical tachometer on the GPU, I also noticed that it is being utilized
100%, at least that's what the LEDs say.
I tried doing a vulkan trace and replay, but the replay does not trigger it.
I'm attaching two vktrace files, first one is my original case, where I render
two frames and exit cleanly (or at least try to). Of note is the never-ending
vkDeviceWaitIdle call (it actually does end as soon as I press the power button
on my PC, more on this in a second). The second trace I attached is one where I
only render one frame and then exit the application (cleanly). Interestingly,
in this case there is no failure
So after the desktop is frozen, I can only press the power button, which
immediately exits xorg server, I again see my tty (I launch startx directly
from tty, no GUI login manager). The control is never yielded back to my tty
though, I can see a snippet of xorg logs but the process has not exited (and
the GPU leds show 100% utilisation still).
Mesa, radv 17.3.3, xorg 1.19.6, linux 4.15.3 with RX Vega 64 GPU.
Let me know if there are additional debugging steps I can take, I can also
provide source code for reproduction steps.
--
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
