Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#66839 - [mesa] Games crash with vulkan backend on mesa 20.1.0-3 (RADV)

Attached to Project: Arch Linux
Opened by Gael (Mploppy) - Saturday, 30 May 2020, 17:42 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 31 May 2020, 07:18 GMT
Task Type Bug Report
Category Upstream Bugs
Status Assigned
Assigned To Jan de Groot (JGC)
Laurent Carlier (lordheavy)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



Vulkan games start and soft-crash in latest testing mesa on RADV hardware (black screen, with mouse usually visible, "themed" and moving).

The game cannot be killed with SIGTERM (unlike normally): it requires SIGKILL.

CPU usage is mildly high while the games hang.

Nothing specific appears in dmesg, in journalctl nor in the terminal, hence the lack of more information.

It looks a lot like something is stuck in an infinite loop somewhere.

Going back to 20.3 removes the problem.

Additional info:

* package version(s): 20.1.0-3 (arch testing)
* config and/or log files etc.: absolutely nothing relevant appears anywhere (terminal, dmesg and log files).
* Sapphire's Nitro+ AMD Radeon 5700XT with stock/default mesa drivers (RADV)

Steps to reproduce:

* Start a vulkan game (make sure it is actually using vulkan): tried with Dota 2 on Steam with vulkan DLC and command line option as well as Divinity Original Sin 2 in Lutris with Wine and DXVK.
* Observe the black screen, mild constant CPU usage and your inability to simply SIGTERM the process.
This task depends upon

Comment by Gael (Mploppy) - Saturday, 30 May 2020, 17:46 GMT
OpenGL works fine btw (at least on Dota 2).
Comment by Laurent Carlier (lordheavy) - Sunday, 31 May 2020, 07:17 GMT
you should file an upstream bug report at
Comment by Gael (Mploppy) - Sunday, 31 May 2020, 13:57 GMT