You are not logged in.
For about 3 months my laptop sometimes hanged after waking up from sleep (which is supposedly s2idle, because my kernel is in lockdown integrity mode). Occasionally, when I type my password into swaylock and receive no visual feedback, it would hang for 5-20 seconds and then unlock.
Today I tried to reproduce this without swaylock by running systemctl suspend and waiting for several seconds before waking up, and after about 5 retries kernel panicked (I couldn't reproduce the issue). Does anybody have a similar problem?
Last edited by flatmoll (2026-01-04 20:40:30)
Offline
I just had panic while trying to wake up normally, and now kernel panics after boot.
Edit: after 2 retries the system booted normally, I cannot say anything about the frequency at which it happens.
Edit 2: after updating kernel to 6.18.2, these errors began to appear during shutdown.
Last edited by flatmoll (2025-12-21 02:50:25)
Offline
Shutdown messages are https://bbs.archlinux.org/viewtopic.php … 4#p2278914
The panics come from rtw89
Can you reproduce them w/
rtw89_pci.disable_aspm_l1=Y rtw89_pci.disable_aspm_l1ss=Y rtw89_core.disable_ps_mode=Y pcie_aspm=offhttps://wiki.archlinux.org/title/Kernel_parameters ?
If not, see which one is the critical one, remove pcie_aspm=off first (as it has the widest impact on power saving)
Offline
I began removing parameters as you gave from right to left, suspending about 10-12 times per cmdline, and was able to reproduce the panic with all of them removed (i.e., when the first was removed). I was also able to reproduce hanging several times throughout.
Offline
Removing?
The idea was to pull them all there to see whether that stabilizes the module.
Offline
It seems to stabilize it with all 4 parameters in (at least I couldn't reproduce panics for now). I then removed the parameters one at at time to see which one is the critical one, and it seems (of course, if testing was enough) that removing the first parameter broke the module.
Edit: should I keep just the first one? Does it have any impact on my system?
Last edited by flatmoll (2025-12-21 14:06:52)
Offline
rtw89_pci.disable_aspm_l1 will disable LP1 (ie. the power isn't cut from the bus) - if that had previously been enabled for your device you'll waste a bit more battery.
pcie_aspm=off would affect all PCIe devices (and thus have the biggest energy price)
You could also try to disconnect the wifi and remove the modules (and later reload them) using https://wiki.archlinux.org/title/Power_ … leep_hooks
Offline
Thanks, I will try to experiment with kernel parameters to figure out where the problem exactly comes from.
For now observations are (edited to match latest):
With first 3 suggested parameters, panic still happens occasionally after wake and boot (I just couldn't catch it when testing).
If panic happens after sleep that was entered due to timeout (in my case - swayidle), next one or two boots will end with panic.
Last edited by flatmoll (2025-12-27 17:32:30)
Offline
Update: I've updated BIOS to P9CN31WW (latest for my laptop), but panics still occur after boot and wake regardless of kernel parameters above. I hope it's temporary regression in kernel 6.18.[1, 2] and not permanent damage to the wireless device itself.
Offline
I hope it's temporary regression in kernel 6.18.[1, 2]
Hope isn't a strategy - is the LTS kernel affected?
Offline
I've been using 6.12.63 for a day, but have not yet been able to reproduce panics.
Last edited by flatmoll (2025-12-30 15:00:54)
Offline
I assume it's been stable for some more days now?
Have you tested 6.18.3? Was/is 6.18.0 also affected?
There's just one patch for the driver in the kernels master since 6.18, https://github.com/torvalds/linux/commi … 9f7273f2ba - which doesn't look like it's gonna fix your problem.
Unfortunately there's like 100 commits for the driver between 6.17 and 6.18.
gromit has several 6.18rc's and bisection kernels in https://pkgbuild.com//~gromit/linux-bisection-kernels/ - assuming it's a regression in 6.18 those can help to narrow down the offending commit.
Offline
Thanks for your continuing monitoring of this issue! The issue seems to be fixed upstream, since I don't see panics with both 6.18.3 local build and 6.18.3-arch.
Edit: 6.18.0 was not affected, but 6.18.1 and 6.18.2 were.
Last edited by flatmoll (2026-01-04 20:40:08)
Offline
I am getting kernel panic(s) with 6.18.5-zen1-1-zen. Disabling wifi with
modprobe.blacklist=rtw89_pci,rtw89_core,rtw89_8852ce stops the panics.
Offline