search

ValveSoftware / SteamVR-for-Linux

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

Serious Sam VR TFE: Completely freezing the system #25

Open leinardi opened 7 years ago

leinardi commented 7 years ago

Your system information

Please describe your issue in as much detail as possible:

It seems that the game completely freeze my system. It happened two out of two time that I started it: I went in the settings menu to change some graphical options and, after applying the changes, the entire OS completely froze. I had to reboot using the Magic SysRq + S-U-B.

Not sure if this issue should be reported here on directly to Croteam.

Steps for reproducing this issue:

  1. Start SteamVR
  2. Start Serious Sam VR
  3. Open the settings and start the autodetection of the graphical settings or manually change and apply some setting.
aronschatz commented 7 years ago

I have this game, too... but mine just crashes after a certain time (it crashes Steam, too). I'm also not sure if Valve should worry about this just yet before nailing down the bugs in things they know work. It might be a Croteam issue, as you suggested.

roothorick commented 7 years ago

Is the system still responsive over network i.e. can you connect over SSH? If so, does killing the game / vrcompositor / vrstatus etc recover the system? Does killing X recover the system? I suspect this is actually a nV driver bug, as I had Destinations do it once and X remained hung even after everything even remotely related to Steam had been forcibly killed.

leinardi commented 7 years ago

Not sure about SSH but I could not switch TTY and also the leds on the keyboard (eg Block Num) where unresponding.

roothorick commented 7 years ago

Going over network is important. It completely bypass local input and graphics; as long as the kernel, Ethernet/WiFi driver, and sshd are okay, SSH will work, which will let you inspect the state of the system when X or the graphics card driver suffers a catastrophic failure.

vpelletier commented 7 years ago

I do have frequent freezes on Debian sid + nvidia v381 using maintainer-provided rules following debian wiki instructions.

System information

Steam client version (build number or date): 1496897923 Distribution (e.g. Ubuntu): Debian sid Graphics driver version (run nvidia-settings): 381.22 Gist for SteamVR System Information: GIST (Beware, this is well after the latest crash, after X restart and unplugging & replugging vive power - please use as general machine info, not as some near-crash system state. Also, not my vive, considering buying one and trying a friend's.). Opted into Steam client beta?: No Opted into SteamVR beta?: No Have you checked for system updates?: Yes

Typical crash symptoms are VR stops tracking, audio buffer is not refilled and loops forever, X output freezes a few seconds later - long enough that I see a CPU core going solid 100% on a running gkrellm. This said, periodically hitting ctrl-alt-backspace, X eventually dies (after several minutes) and the machine recovers. But the whole session is not brought down with it, some vr process keep running (some in D state, so there may be a driver or otherwise kernel-side issue alongside the segfaults below).

Checking via coredumpctl vrcompositor looks like it is the first thing going down, in CVRSharedState::GetSharedStatePointer, and vrmonitor gets into _XIOError. GIST of a quick coredumpctl session