SteamVR crashes system after setting nvidia Force Full Composition Pipeline

steamvropen

ValveSoftware/SteamVR-for-Linux#210 · opened 2019-07-11 by SlickMcRunFast · updated 2020-12-16 · 6 comments · github

SSlickMcRunFast 2019-07-11 github

Your system information

Steam client version (build number or date): 1562626460, Jul 8 2019
Distribution (e.g. Ubuntu): Ubuntu 18.04 64 bit
Graphics driver version (run nvidia-settings): 430.26
Gist for SteamVR System Information: https://gist.github.com/SlickMcRunFast/c4e1a26db6f75a44882097687edca2d7
Opted into Steam client beta?: [Yes]
Opted into SteamVR beta?: [Yes]
Have you checked for system updates?: [Yes]

Please describe your issue in as much detail as possible:

From nvidia-settings I enabled "Force Full Composition Pipeline" as an attempt to stop screen tearing. Immediately after I start SteamVR and about 5-10 seconds later my system becomes unresponsive. I took a picture of a stack trace (no idea what log its in) listing a bunch of nvidia calls that I can post if it required.

Steps for reproducing this issue:

Run from terminal: nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }" (ref: https://unix.stackexchange.com/questions/510757/how-to-automatically-force-full-composition-pipeline-for-nvidia-gpu-driver)
Start SteamVR
Greet Mr.Freeze

SSlickMcRunFast 2019-07-31 github

Doesn't seem to happen with 430.34.

SSlickMcRunFast 2019-08-03 github

Ahh still happening.

Eel8 2019-11-24 github

I can confirm this, seeing it on all versions I tried so far (latest is 440.26 for me). Also, disabling ForceFullCompositionPipeline means I get screen tearing in all games, not only VR.

Tthomasvring 2019-11-26 github

Leaving FullComp on and then starting SteamVR completely locks up my system, requiring a hard reset. Turning FullComp off solves this. I do not experience screen tearing in VR with FullComp off, everything outside of VR is a teary mess. Tested with PopOS, Kubuntu and Manjaro, all the same behavior.

Sslackerbob 2020-07-08 github

I can also confirm this issue on Arch Linux:

Steam client version (build number or date): 1594079536, July 6 2020
Distribution (e.g. Ubuntu): Arch Linux 64 bit
Graphics driver version (run nvidia-settings): 440.100-1
Gist for SteamVR System Information: https://gist.github.com/slackerbob/d5f0f04ab7d1ac52433a89b221555afc
Opted into Steam client beta?: Yes
Opted into SteamVR beta?: Yes
Have you checked for system updates?: Yes

I'd say it's maybe a 50/50 shot of my entire system locking up when starting steamvr with Full Comp turned on.

Eexpipiplus1 2020-12-16 github

Can confirm too on NixOS.

Is is possible for the launcher to detect this setting and abort with a helpful message instead of locking the system?

Nothing extracted yet.