search

ValveSoftware / SteamVR-for-Linux

Issue tracker for the Linux port of SteamVR
932 stars 45 forks source link

Steamvr freezes Steamvr freezes with error 203 #186

Open silelmot opened 5 years ago

silelmot commented 5 years ago

Hardware:

Issue Details:

When running steamvr with my new vive pro games like beatsaber, pavlov but also native linux games like serious sam VR run a few minutes after the hmd-screen freezes and steamvr errors with error 203. After the new beta update beatsaber freezes after 2 songs instead of a half one, like before.

The strange thing is, if i unplug the vive pro and plug in my still available vive 1 i can play without problems.

notgne2 commented 5 years ago

Can confirm I also have this issue on Ubuntu 18.10, tried with and without SteamVR beta, and tried with NVidia drivers both 418.43 and 410 on my GTX 1080.

I don't have a standard Vive to test with, only my Vive Pro, though I have not found anybody else who has the issue but not a Vive Pro.

I also came across this Reddit thread https://www.reddit.com/r/Vive/comments/ajuycz/new_vive_pro_linux_headset_display_freezes/

Can't seem to find any errors in logs, screen on headset will simply freeze after some time giving huge amounts of motion sickness, and some time after that SteamVR will crash with error code -203. The real time frame information will also freeze at the same time as the headset viewport.

Not sure if this is related, but I also have issues dragging the SteamVR information windows, on my tiling window manager XMonad this affects both the settings window and the status window, whereas on the stock XFCE window manager this only affects the settings window. When dragged the viewport in the headset will jitter a lot with huge delays between frames, and the windows will take about 10 seconds to catch up with where you dragged them, feels like I'm running windows. Figured this might be related since I have not seen this issue mentioned anywhere else.

notgne2 commented 5 years ago

Another note, disabling reprojection stuff (shift+a in preview window) seems to give me a way longer time in VR before a crash, though I have only tested a handful of times so this may be a coincidence

Casuallynoted commented 5 years ago

Same issue here, also on a Vive Pro. Haven’t gotten error 203 yet however, just a total system freeze.

Casuallynoted commented 5 years ago

Tried again today, was able to complete room setup. Noticing that it’s not a total system freeze, but it is locked up so much that accomplish a basic task like trying to close SteamVR can take anywhere up to 30 minutes. Going to send logs shortly once my computer is usable again.

GitHawk Upload by Casuallynoted Been stuck at this for about 10 minutes so far.

Edit: 30 minutes later and it hasn’t progressed much past this point, can’t click anything and get it to register. My PC’s fan is getting much louder. What is SteamVR doing that causes this?

GitHawk Upload by Casuallynoted

Casuallynoted commented 5 years ago

Alrighty, here are some logs.

vrclient_steam.txt vrclient_steamvr_room_setup.txt vrclient_vrcompositor.txt vrclient_vrdashboard.txt vrclient_vrmonitor.txt vrclient_vrstartup.txt vrclient_wine64-preloader.txt vrcompositor.txt vrdashboard.txt vrmonitor.txt vrserver.txt vrsharedresourcemanager.txt

silelmot commented 5 years ago

I have exactely the same behavior and one of my 6 cores is running on 100% the whole time steamvr is running and i think thats the problem.

Casuallynoted commented 5 years ago

I do think this may be an issue with the Vive Pro in SteamVR for Linux in general and if so that’s really off putting since the HMD has been out since early 2018.

Jaystified commented 5 years ago

Any news on this issue?

notgne2 commented 5 years ago

@Jaystified

Not that I know of, I tried again a few days ago just in case it got patched under my nose to meet with the same issue - freeze after like 30 seconds, quicker if more intensive, audio issues until pulseaudio -k which fixes audio for about an hour if nothing crashes.

It seems like the devs overlooked this whole headset (in combination with NVidia drivers at least), and they probably won't go back to it any time soon (I wonder if the new Valve headset will work?). Though I still hope their testing did happen just under specific repeatable conditions, not just that they never tested for over a minute.

Casuallynoted commented 5 years ago

I’m working with someone from Valve over email to try to get it resolved! If you guys are both on Nvidia, could you do this for me?

“Looks like the 203 error is more of a legitimate compositor crash on our side, rather than a driver lockup for the whole system. Can you query the driver version from nvidia-settings so we can try to reproduce it on this end?”

silelmot commented 5 years ago

i am using Arch with Nvidia drivers: 430.14

thetornadotitan commented 5 years ago

Ubuntu 18.04.2 LTS AMD® Fx(tm)-8350 eight-core processor × 8 GeForce GTX 1080/PCIe/SSE2 Gnome 3.28.2 OS 64-bit Memory 11.6 GiB

nVidia driver version 430.14

Locks up entire computer when headset is connected via USB and HDMI. Can open SteamVR with out headset plugged in and can change settings. Locks up entire system wether or not VR dashboard and/or VR Home is enabled or disabled The option for disabling re-projection seems to be gone so I cannot try that as has been mentioned in other issues regarding computer locking up.

notgne2 commented 5 years ago

I've tried with nvidia driver 418.43, 430, and 387.

I have only had it freeze my PC or max out a core a few times, mostly the render will just freeze and display the same image in VR for a few minutes, then eventually I will get the error and SteamVR will exit on the headset.

Jaystified commented 5 years ago

I've also had the same problem using GeForce RTX 2070 with driver versions 430, 418 and 390.

cbsghost commented 5 years ago

Same problem. I have both Vive and Vive Pro, but only Vive Pro freeze the system.

While the graphic driver may have some bugs, I've found it is not the main reason causing system to freeze. There is a project called SteamVR-OpenHMD, which supports Vive Pro as well. I compiled it and tested with SteamVR. It has NEVER crashed or freeze the whole system while running any OpenVR games. In order to let the OpenHMD driver being selected by SteamVR runtime, the builtin lighthouse driver must be disabled. During testing OpenHMD, I found the GetPose function has a little chance to stuck and return late. The function stuck in when games is busy, such as loading a bunch of resource.

So I guess the main reason causing freeze is in the builtin SteamVR lighthouse driver (driver_lighthouse.so). It might have some deadlock in the pose tracking thread, and lock up the entire VR compositor.

notgne2 commented 5 years ago

I've just noticed adjusting the resolution of an application down to 20% will avoid the issue for much longer than usual, so it could still either be something that happens over time or just be reducing the chance of an occurrence

CarpeNecopinum commented 5 years ago

In my tests, the freeze will occur after reprojection switched off and on again (or regular missing frames appearing and reappearing). As seen in the SteamVR settings graph:

image

The app was running in the orange area (reprojection active) for several minutes. Then I looked up (fever things to render, shorter frame times), which got me into the green area. Looking down again SteamVR then locked up almost immediately.

image

Same procedure as with the other graph, but reprojection disabled (with Shift-A in the Mirror). The app ran for several minutes with regularly missed frames. Then I looked up, so I don't miss frames anymore. Looking down then froze the app (though before SteamVR graphed the first missed frame).

BenjaminNavarro commented 5 years ago

I also have this issue on an Archlinux computer with an RTX2080 and NVIDIA 430.26. It always happened to me from time to time but today it started to crash way more often, making the VR system unusable. I think I tried more or less everything to lower the number of crashes but it really seems completely random in the end...

sheepdestroyer commented 5 years ago

big freezes, valve index, fedora 30, RTX2080 and NVIDIA 430.26

beniwtv commented 5 years ago

Same here on my Valve Index. Beat Saber seems to work fine, but other games freeze (quickly reproducible are Payday 2 VR and Tales of Escape). I am using an AMD Radeon VII on Mesa 19.2.1

I notice when the crash happens I get this in dmesg: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] ERROR Waiting for fences timed out or interrupted!

Followed by audit messages of a coredump, seems like from vrcompositor. I think it saved into /tmp/dumps - I saved the files there, if it helps I can give them to you guys somehow.

Jaystified commented 5 years ago

Is this still an issue? Has anyone tried this with NVIDIA 435.21?

BenjaminNavarro commented 5 years ago

Probably sine as mentioned by cbsghost this is not an NVIDIA issue but a lighthouse one. I can test it this week to be sure if necessary

ricargoes commented 5 years ago

hey everyone, this issue along with the audio distortion one completely disappeared with SteamVR 1.8. I can finally play with my Vive Pro on Linux!

There is a performance hit which makes some games unplayable for me and the steam overlay is not working whatsoever. But those are the mayor issues I have found

Tested on: Manjaro Linux Steam client beta channel SteamVR 1.8.20 Vive Pro Ryzen 3600 NVidia GTX 970, driver 435.21

ghost commented 5 years ago

This happens on even the most recent version with the rx 5700 on both free and pro drivers on both ubuntu 18.04 and manjaro with the 5.3 kernel System would max to 100% cpu usage on my 3700x on ubuntu and manjaro completely hangs, requiring full restarts to do anything in either with an htc vive Fix this

Jaystified commented 4 years ago

Appears to be fixed for me in the latest VR beta (did not test non-beta).

GilgameshofUT commented 4 years ago

I wanted to add to this report as I can reliably recreate the issue on a clean install of Steam. Occurs using non beta, main beta and linux beta.

  1. Go into the default steam home
  2. Open the menu and select items, then panels
  3. Select big picture panel
  4. Big picture panel appears and instantly the picture freezes, after a few seconds it is a black screen. SteamVR says Uh Oh! needs to restart error -203.

This is 100% repeatable for me. I have purged and reinstalled Steam. Installed it under different user accounts. Purged and reinstalled drivers (mostly Nvidia 440 and 435). I have tried it with steam installer packaged with Mint and the deb file from the steam web site (why can't everyone agree on where the Steam library should be and at least offer to move it around if its not in the place they want?) I have tried it with multiple steam accounts, some owning a few games the other owning about 200. There is a separate bug dealing with the overlay menu and having multiple steam library folders that I believe is unrelated and I will write up separately. I have verified this bug is reproducible with only one library folder and a fresh install, no games other than SteamVR installed.

OS: Linux Mint 19.3 Tricia KERNEL: 4.15.0-74-generic CPU: AMD Ryzen 5 2600X Six-Core GPU: NVIDIA GeForce GTX 1660 SUPER GPU DRIVER: NVIDIA 440.44 RAM: 32 GB

GilgameshofUT commented 4 years ago

Just verified this crash is still a thing with 1.10.2

onzyone commented 3 years ago

seeing the same issue on 1.19.3

Bioflakes commented 2 years ago

Replying to https://github.com/ValveSoftware/SteamVR-for-Linux/issues/186#issuecomment-573997031

Same for me, on a win11, 5900x and RTX 3070 system. I suspect the GPU gets overloaded. I'm using a 3440x1440p Ultrawide and a second, vertical (flipped portrait mode) 4k display, and every time I try to open the 4k display in desktop viewer, it crashes.