FS#72884 - [mutter] Nvidia + GBM breaks Vulkan applications

Attached to Project: Arch Linux
Opened by George (Vash63) - Tuesday, 30 November 2021, 14:14 GMT
Last edited by Toolybird (Toolybird) - Friday, 02 June 2023, 07:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: Upgrading from 41.1-1 to 41.1+r20+ge3931f7b8-1 caused GNOME Wayland to use GBM instead of EGLStreams on my system. Unfortunately this has a known issue on Nvidia (see bug report below) that breaks multiple applications.


Additional info:
* Upstream bug report: https://gitlab.gnome.org/GNOME/mutter/-/issues/2034
* Example errors in logs:
gnome-shell[1608]: Window manager warning: Failed to write cursors buffer data: Cannot allocate memory
kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Failed to map NvKmsKapiMemory 0x0000000019a37696

Steps to reproduce:
Upgrade to 41.1+r20+ge3931f7b8-1
Launch Gnome Wayland
Launch a Vulkan game on Steam (Tested with the Quake 1 remaster)
This task depends upon

Closed by  Toolybird (Toolybird)
Friday, 02 June 2023, 07:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  See comments
Comment by George (Vash63) - Sunday, 12 December 2021, 12:44 GMT
Is it possible to get the package reverted to 41.1-1? mutter has not released any stable versions with MR2067 applied and there are known bugs. In addition, as this MR ONLY applies for Nvidia users and this regression impacts the exact same set of users, there is truly no benefit to including this unreleased patch as default in a supposedly stable package.
Comment by Gerhard Bogner (slashME) - Thursday, 16 December 2021, 00:57 GMT
for me vulkan seems to work on wayland, at least with vulkan-icd-loader != 1.2.199
Comment by George (Vash63) - Thursday, 16 December 2021, 08:39 GMT
@slashME - This happens over time apparently, first launch might work but try again after consuming some VRAM or waiting. It's a background VRAM memory leak. This isn't theoretical, the issue was acknowledged upstream by both Gnome and Nvidia devs and a fix is pending in Nvidia 510 drivers coming next year per:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2045#note_1335845

In the meantime an update including this MR plus the listed env var being set works as a workaround: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2132

Unfortunately it seems at this rate it will likely stay broken on Arch until Nvidia gets their full fix out in January.
Comment by Gerhard Bogner (slashME) - Thursday, 16 December 2021, 11:04 GMT
i might not have run into this because i tend to turn off the pc over night - i imagine it takes a while for leaking cursor textures fill up 10 GB...
Comment by George (Vash63) - Thursday, 16 December 2021, 13:29 GMT
Might also be impacted by display refresh rate and input rate. I'm on a 1000Hz mouse with a 240Hz display which could cause more texture updates than normal. I duplicated it with less than an hour of playing Quake Remastered (Vulkan), closing it, doing some stuff in Firefox/Discord and then attempting to open the game again. I've since downgraded to 41.1-1 and blacklisted this package from updating until the issue is resolved.
Comment by George (Vash63) - Wednesday, 12 January 2022, 15:27 GMT
This can be closed as soon as Nvidia 510.39.01 or higher hits the repos as it no longer has the bug exposed by this mutter update

https://www.nvidia.com/Download/driverResults.aspx/184911/en-us

Loading...