Complete GPU crash on X11 with "Force Full Composition Pipeline" and VK_KHR_present_wait! 100% reproducible!

Graphics / Linux Linux
1

This crash has been confirmed by Valve engineers.

Steps to reproduce:

  1. NVIDIA driver 535+.
  2. I’ve tested this with RTX 2070 Super. But I assume every card is affected.
  3. Must be on X11.
  4. Enable “Force Full Composition Pipeline” in NVIDIA Settings.
  5. Use DXVK 2.3 release, which has whitelisted the usage of VK_KHR_present_wait on NVIDIA drivers.
  6. Play any game that uses DXVK. The desktop will freeze 1-2 seconds after the game opens up and there is no way to unfreeze it.

There are two discussions about this crash on GitHub:

1 Like
2

Someone also made a post about it on your Windows forums, so I’ll link to that just for completeness:

https://www.nvidia.com/en-us/geforce/forums/support/527697/linux-games-freeze-when-using-force-composition-pi/

3

Same here, most of the games are starting to a black screen and doesn’t run at all if using Force Full Composition Pipeline and VK_KHR_present_wait.
X11 here with GTX 1080Ti.

4

I think I’ve been experiencing this issue with Cyberpunk.

For me, it’s not a complete deadlock - rather, rendering slows to about 1 frame per minute (yeah ~0.016FPS) and won’t even let me jump to a terminal (eg ctrl+alt+F1) until it’s time to render the next frame.

Alt+tabbing to another application (also needs to wait for frame render time) seems to unlock rendering and the game runs normally behind other windows - however, refocusing the game puts the desktop back in its near-deadlocked state.

For some reason, downgrading VKD3D 2.10 to 2.9 prevents this issue from occurring - perhaps 2.9 doesn’t expose VK_KHR_present_wait?

5

We have a bug filed 4174755 internally for tracking purpose, team is Woking on it.

1 Like
6

I’ve had the exact same experience described above, though the issue persists even after double checking that “Force Full Composition Pipeline” is disabled in NVIDIA Settings (and enabling then disabling the option, as well).

7

Odds are it’s still on under the hood, despite what the settings menu is telling you, try running the console command nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceCompositionPipeline=Off, ForceFullCompositionPipeline=Off }"

I found that if I disabled it this way, i simply cannot run my display at it’s full refresh rate, and it dropped down to 30hz.

8

I confirm that disabling ForceFullCompositionPipeline works around this issue.

Curiously, it was unchecked in nvidia-settings despite being enabled in xorg.conf.d/90nvidia.conf, which may confuse some folk.

9

I also have this issue, waiting for nvidia to hopefully fix