You are not logged in.
All the linux, linux-zen & linux-rt standard kernels lock the system completely on building ayugram-desktop from AUR (uses 100% of CPU load and normally swaps ca 8 out of 32 GB with 16 GB RAM). Older versions had no problem. Swap file used and required to hibernate. Same happens in recovery console mode from boot (makepkg).
Only the current linux-lts v6.6.23 still allows building.
Hints, fixes, solutions?
Last edited by bibies (2024-04-23 15:43:33)
Offline
There are some reports with issues with zswap in 6.8 kernels, try disabling it with the
zswap.enabled=0
kernel parameter.
See e.g.: https://bbs.archlinux.org/viewtopic.php?id=294360 and/or https://bbs.archlinux.org/viewtopic.php?id=294481
Offline
zswap.enabled=0
Thanks, have to try. Will that affect performance severely but keep swap alive and allow hibernation?
Offline
Like all things swap this strongly depends on what exactly can even be compressed and whether the backing device you're running on benefits more from the compression than not compressing things. Generally having to swap is always a perf hit, chances are somewhat mitigated on SSDs
Offline
Not a solution but until a permanent fix appears you can control zswap manually:
place lines below in ~/.bashrc
zswap_ctl='/sys/module/zswap/parameters/enabled'
alias zswap='cat $zswap_ctl'
alias zswap0='su - -c "echo 0 > $zswap_ctl" ; zswap'
alias zswap1='su - -c "echo 1 > $zswap_ctl" ; zswap'
Last edited by bibies (2024-04-05 21:07:22)
Offline
Im having the same issue running Endeavor OS Even after using the zswap trick my laptop locks up and wont continue until after force restarting it.
Offline
Im having the same issue running Endeavor OS Even after using the zswap trick my laptop locks up and wont continue until after force restarting it.
Since newer kernels like version 6.8./5...7, i.e. 6.8.7-arch1-1 and 6.8.7-zen1-1-zen (both are updated the same day) looks like none freezes happened anymore (zswap enabled as it normally should be). Recently ayugram build with 6.8.6-zen1-1-zen kernel went just fine, so there's a probability the bug was already fixed. Maybe somebody who knows for sure could confirm, otherwise for me a couple of more builds would indicate the case is closed.
Last edited by bibies (2024-04-22 16:15:25)
Offline
As per this extra confirmation I'd consider the issue as solved.
Offline
Please formally mark it as such by editing your thread title in the first post.
Offline