Swap
I have been running Bazzite for about 3 weeks now, and for the most part it runs quite well. A few minor hickups here and there but nothing I have not been able to figure out and fix.
However, one thing that has been pretty consistently happening to me is when I have my computer on for a long time and play a lot of games over that time I get a freeze when trying to shutdown. I had no idea what was causing it, so I looked at the logs and found 'Failed deactivating swap dev-zram0.swap' and 'Failed deactivating swap dev-disk-by\x2ddiskseq-3.swap'
I found a post on a Fedora forum that talked about how they also got shutdown freezes when their swap was full (As seen in the System Monitor).
It is a bit frustrating, because it leads to my computer not shutting down properly quite often as I use my computer a lot.
I don't really know what to do beyond running the 'swapoff' and 'swapon' commands every now and then to clear it.
10 Replies
so that's why sometimes my PC takes 3 business days to shutdown. the ideal solution is turning off swap after most services have shutdown, will take a look later š
better file an issue on github
Issue posted on github, let's see where it goes. š
pretty sure bazzite uses zram and no swap by default
see bazzite docs
It uses 4G zram and a very aggressive zswap config
dunno then, maybe try following the guide to make a bigger swap
I haven't had this issue since I turned off zswap and zram (for different reasons)
Enabling Hibernation in Bazzite Desktop Images - Bazzite Documentation
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices.
I found a little bit of a workaround sollution for this to use until it gets a proper fix. š
In the file: zram-generator.conf you can set a limit with 'zram-resident-limit' and as long as you set it to lower than your current swap amount it should never hit max and therefore never hit this problem.
Here is an example of how my file looks with this in mind.
I also have this exact issue.
Will try this workaround. Really appreciate your update with a temporary fix