#Stellaris causing total desktop freeze requiring hard reboot

97 messages · Page 1 of 1 (latest)

acoustic ridge
#

I'm not sure this is the correct forum to post this, but this has been the most helpful forum I know of, and if anything it might help me straighten out some question marks

So I enjoy playing Stellaris and in recent weeks the game has been having problems with totally and completely freezing my PC after a few hours of running. I cannot for the life of me get out of the frozen state without hard-rebooting. This is concerning since you shouldn't make a habit of doing that.

The behaviour is really bizarre, and I cannot find any logs to look at.

rancid hearth
#

Could be a Proton bug, or an amdgpu driver hang

#

VRAM running out too, perhaps

#

You can try switching between Proton 10 and Proton Experimental

#

Update the kernel to version 6.17 to get a more recent version of amdgpu

#

And check your VRAM usage (nvtop is a great tool for this)

acoustic ridge
#

But if it is a GPU driver hang, it would explain great many things.

rancid hearth
#

oh so it's native

#

ok then

#

Then, take a timeshift snapshot and upgrade the kernel, you can always boot into 6.8 and purge 6.17 later on.

#

Then, install nvtop and check VRAM usage while playing.

#

There could be a VRAM leak

acoustic ridge
#

Thank you for the pointers!

acoustic ridge
#

Ok, starting this. Gonna remember how to get into GRUB in case shit hits the fan and I can boot back to 6.8.

#

Posting this for posterity so I can access it from my phone if needed.

#

Posting new neofetch for kernel verification. I should probably install fastfetch or something at some point so I don't use deprecated tools.

#

Let the experimentation begin

rancid hearth
#

You must press ESC once at the manufacturer logo

acoustic ridge
acoustic ridge
#

After about three hours of gameplay I've not noticed anything problematic. This looks good! I think.

rancid hearth
#

can you show the output of journalctl -b -X | grep -E "amdgpu|drm" where X is the number of sessions behind the current one where it crashed last

acoustic ridge
#

I wish I knew how to find the session number out.

rancid hearth
#

You can experiment

#

First line should say "Linux ... 6.8.0 ..." since it only crashed in that kernel

#

And then, log should be interrupted abruptly, due to the unclean shutdown

acoustic ridge
#

Hmm... Okay

#

How do I calculate this? I have a hunch on when this might have happened. But I assume every boot is considered its own boot, yes?

rancid hearth
#

Wdym by that

#

all user sessions are saved by journald

acoustic ridge
#

Yeah, but like, how do I trace backwards? By what accounting should I consider?

rancid hearth
#

Try doing journalctl -b -1 | grep -E "amdgpu|drm", if it doesn't meet the requirements, replace -1 with -2 and keep going

acoustic ridge
#

OK!

rancid hearth
#

actually

#

first, run journalctl -b -X, check the output, and then run journalctl -b -X | grep -E "amdgpu|drm"

#

since grep won't show everything

acoustic ridge
#

Oh that is a lot of text

rancid hearth
#

use page up/down to scroll fast

acoustic ridge
#

Okay so the most recent one (I think) is from before I installed 6.17

#

I forget how to get out of the terminal scroll.

#

-# I figured it out

#

OH! I think I got something!

rancid hearth
#

yeah seems like amdgpu is having a tough time in the second log

acoustic ridge
#

Big sad

#

Anyhow, I'll run more attempts in the week to come before new trade school course kicks up a suffering like hell. We'll see how it goes, but it looks promising right now.

acoustic ridge
#

It was not promising. Stellaris is getting worse. It's the only game that gets issues on my PC so either the linux build is borked on AMD or my GPU is eating shit, which is something I don't need right now.

I'm hesitant to call out my GPU since it runs every other game I have just fine. It's just Stellaris causing it to eat shit.

#

Like there is something with Stellaris that causes the GPU to 'wedge' itself.

acoustic ridge
rancid hearth
acoustic ridge
#

I'm still writing off hardware failure since more load demanding games are working fine for hours on end.

rancid hearth
#

Then perhaps mesa doesn't play well with this game, due to it being unoptimized

acoustic ridge
#

Yeah pretty much

#

I might send paradox a bug report, but I need to test it completely clean of mods (I'm pretty sure it's a mod causing this issue)

rancid hearth
#

Clear the mods then

#

If the mods don't change how the game renders then it's unlikely

acoustic ridge
#

I will do it tomorrow when I'm not as sleepy from choreing all day

acoustic ridge
#

After a few hours of testing on a clean save, it's become apparent that this issue persists. A thought comes to me. These issues only came to light after I updated to 22.3. Maybe correlation? Not willing to make it an absolute thing though.

I might opt to run Stellaris through proton in the future, though.

#

If it is a driver hang, I wouldn't know how to fix it.

rancid hearth
#

22.3 has no base packages changes. So no kernel, driver, and libraries changes. The only thing it changes are Linux Mint components themselves, so for example the desktop environment, window manager, etc.

#

The only correlation between the upgrade and the game failing could be a buggy implementation in either the desktop environment and/or the window manager

acoustic ridge
#

Mint 21.3 used 5.16-something as its default kernel, though. So it's quite a difference between kernels. Still, I am far too unskilled in these things to make any suggestions worth entertaining beyond amateur conjecture.

#

Either way, the amount of time and skill needed to figure this out properly is beyond my means. I'll just speak to paradox to see whether or not they borked something on their end.

#

Which is where I am leaning, save for drivers.

low compass
#

idk if I can be of help since Im still pretty new to linux overall but I had the same issue tho with a different game, overwatch. The whole system would freeze right before I got into a match and after some research, apparently it happens when memory runs out and since mint doesn't know how to handle it it just freezes until u reboot it. I had pretty low memry, about 8 gigs so I simply increased swap with some healthy headroom (about 32gigs) and the issue was fixed(I also disabled zram). I run ow throu steam proton 9.x I think. Also I havent read the full thread so ignore if the issue has already been solved.

rancid hearth
#

it is by default

acoustic ridge
rancid hearth
#

System Settings -> General

acoustic ridge
rancid hearth
#

it's a good idea to keep it disabled

acoustic ridge
#

Ah okay! Will do!

#

Any particular reason?

rancid hearth
acoustic ridge
rancid hearth
#

also is 'Disable compositing for fullscreen windows' enabled?

#

that could help

acoustic ridge
#

Okie dokie! I'll test it some more during christ-goes-to-space day since there are no assignments.

rancid hearth
#

yeah do enable it

#

reduces GPU load

acoustic ridge
#

Okay! Thank you, Temmie! You're ever so helpful!

#

One million temmie flakes for you.

low compass
#
  1. I understand but the 32GB is how much I was willing to lose. For some reason overwatch uses so much memory on linux and whenever I play, 16GB out of the 32 were being used up. Thankfully I have 1TB so 32 isnt too bad
#
  1. That was also a major concern of mine when I first heard of it but apparently it would take(and do not quote me on this lol) billions of writes to wear down the ssd and that's yrs which I assume at that point I'll have upgraded.
#
  1. idk I can't testify it doesnt for everyone but in my limited experience it hasnt had much of an impact in speed.
low compass
acoustic ridge
#

I also didn't have time yet

low compass
acoustic ridge
#

I am sure we will

rapid basalt
#

@low compass Bazzite link should work for you now, also your message;

here's the link to the docs, https//docs.bazzite.gg/Advanced/swapfile/?h=swap

acoustic ridge
#

Sadly none of the suggested fixes (applicable) have helped. GPUwedged itself again after just a few minutes of running. This is really strange.