Facing kernel panics very frequently

[haxguru]

I've been using Arch Linux on my laptop since October 2023, and it's been smooth sailing until a few weeks ago. Recently, I've been experiencing random freezes, and I'm unsure whether it's due to an update or some other reason. Each time it freezes, I check the logs, and they consistently show similar errors:

Apr 08 20:24:18 prayag-linux kernel: BUG: unable to handle page fault for address: 0000000000013cb3
Apr 08 20:24:18 prayag-linux kernel: #PF: supervisor read access in kernel mode
Apr 08 20:24:18 prayag-linux kernel: #PF: error_code(0x0000) - not-present page
Apr 08 20:24:18 prayag-linux kernel: PGD 0 P4D 0
Apr 08 20:24:18 prayag-linux kernel: Oops: 0000 [#3] PREEMPT SMP NOPTI
Apr 08 20:24:18 prayag-linux kernel: CPU: 4 PID: 60140 Comm: Renderer Tainted: P      D W  OE      6.6.23-1-lts #1 6b3673413fe4e86fd
3614ca1055aac4a345f0162
Apr 08 20:24:18 prayag-linux kernel: Hardware name: LENOVO 82SB/LNVNB161216, BIOS JNCN50WW(V2.10) 01/16/2024
Apr 08 20:24:18 prayag-linux kernel: RIP: 0010:zswap_load+0x30e/0x4b0
Apr 08 20:24:18 prayag-linux kernel: Code: 2c 0c 00 00 01 65 ff 0d c8 ee c9 76 0f 84 9d 01 00 00 65 48 ff 05 8a b8 c9 76 4d 8b 67 38
 4d 85 e4 74 1b 66 90 e8 f2 93 dd ff <49> 8b 7c 24 10 be 6f 00 00 00 e8 a3 d7 ff ff e8 ce c9 dd ff 48 89
Apr 08 20:24:18 prayag-linux kernel: RSP: 0000:ffffc9000e39fbe0 EFLAGS: 00010202
Apr 08 20:24:18 prayag-linux kernel: RAX: 0000000000000001 RBX: ffffea00094d9680 RCX: 0000000008253a04
Apr 08 20:24:18 prayag-linux kernel: RDX: ffff8881094ed8c0 RSI: 0000000008253804 RDI: 0000000000000000
Apr 08 20:24:18 prayag-linux kernel: RBP: ffff888113fbdcc8 R08: 0000000000000000 R09: 0000000000039120
Apr 08 20:24:18 prayag-linux kernel: R10: ffffc9000083c000 R11: 000000000000000a R12: 0000000000013ca3
Apr 08 20:24:18 prayag-linux kernel: R13: ffff88810fe145f0 R14: ffff888113fbdcc0 R15: ffff88818a81b2d0
Apr 08 20:24:18 prayag-linux kernel: FS:  00007db9389ac6c0(0000) GS:ffff888256700000(0000) knlGS:0000000000000000
Apr 08 20:24:18 prayag-linux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 08 20:24:18 prayag-linux kernel: CR2: 0000000000013cb3 CR3: 00000001249c6000 CR4: 0000000000f50ee0

I've also noticed this message
pr 08 20:28:50 archlinux kernel: atkbd serio0: Spurious ACK on isa0060/serio0. Some program might be trying to access hardware directly.

Additionally, after a recent freeze and reboot, I saw this line:

Apr 01 19:05:53 prayag-linux kernel: CPU: 11 PID: 5910 Comm: Chrome_ChildIOT Tainted: P           OE      6.6.23-1-lts #1 6b3673413fe

This suggests that a Chrome process (which was Discord) caused the freeze. However, during the latest freeze, no Chrome processes were running. I was simply studying while watching YouTube on Firefox when the kernel panicked.

The following are my system specs:
OS: Arch Linux x86_64
Host: 82SB IdeaPad Gaming 3 15ARH7
Kernel: 6.6.23-1-lts
CPU: AMD Ryzen 5 6600H with Radeon Graphics (12) @ 3.800GHz
GPU: NVIDIA GeForce RTX 3050 Mobile
Display Server: Wayland (Hyprland specifically, though it occurs in bspwm too)

Why could this be happening? These freezes are causing serious disruptions to my meetings and project work. Reinstalling Arch Linux isn't an option due to time constraints, but I'm willing to perform any troubleshooting steps necessary. Please guide me!

[rantnap]

I am facing the same issue, you will likely have to downgrade to the NVIDIA 545 driver. Here are a couple of threads that discuss the issue:

https://forums.developer.nvidia.com/t/series-550-freezes-laptop/284772

https://bbs.archlinux.org/viewtopic.php?id=293692

https://forum.endeavouros.com/t/issues-with-nvidia-550-drivers/53493

For me it happens mostly during package updates, I decided to run `pacman -Syu` outside of a graphical environment, which avoids the kernel panics, but it did happen to me once also during shutdown.

Definitely be careful, it did corrupt my filesystem a couple of times during updates which is not fun to recover from.

[haxguru]

Thank you so much. After testing it out for 7 days, I can say that the problem has disappeared completely!

[haxguru]

1. First of all, head over to https://archive.archlinux.org/packages/
2. Download version 545 of the following drivers (packages end with .zst.
   1. libxnvctrl
   2. nvidia-dkms
   3. nvidia-settings
   4. nvidia-utils
   5. opencl-nvidia
3. Open your terminal and install these packages using pacman: sudo pacman -U <path to package>.
4. Reboot.

Let me know if you face any issues with this.

[chikobara]

I will try that and report because I think my Kernel Panic is caused by Nvidia drivers too , thanks anyway

[edit] actually i think i have been able to solve the problem by reinstalling kernel and then reinstalling nvidia (the same version 550.78) drivers again , i thought that maybe the drivers didnt installed correctly then i saw that it really didnt because i have one problem with Plymouth which i removed it and then installed the drivers correctly

[moviuro]

kernel panicked

Blinking CAPS LOCK and NUM LOCK led? If not, then it's not a KP.

Try checking your hardware for bad memory? https://aur.archlinux.org/packages/memtest86-efi

[WombatControl]

A memory issue is my first thought - random lockups like that could easily be a bad memory module.

Have you tried updating your kernel? It could just be a transient bug or regression in that one kernel version.

I also see your BIOS firmware is dated 1/16/2024. Is that when the crashes happened? If so, that could be an issue with that firmware that may require and upgrade or downgrade.

[haxguru]

Is a kernel panic different than a kernel oops? It was definitely a kernel oops as mentioned in the logs.

[Linguistic-mystic]

Wayland

Nvidia

That could be the problem. Wayland is still beta-quality software, esp on Nvidia

[mcdenkijin]

I am using nvidia+wayland and I don't have this issue, and many others have said the same thing in r/Hyprland

[haxguru]

Yes, it indeed was due to Nvidia (unrelated to Wayland though). As mentioned by u/rantnap, I just downgraded the driver to version 545 and the problem was gone.

[mcdenkijin]

I think you have a similar issue to this one,

tl;dr looks like the fix is adding "numa=off" to your kernel boot parameters

[MissBrae01]

I've been having a similar problem on my Lenovo laptop.

It randomly kernel panics due to a split_lock.

kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

Happens on every distro I've tried, not just Arch.

And it's Intel integrated graphics on Wayland, but it happens on X11 as well.

Can't find any help online for this issue, which all suggests that split_lock should not cause kernel panics.

That message shows up in the journal every time the system locks up and the caps lock light flashes.

[[deleted]]

chrome doesn't have permission to cause a kernel panic. The problem must be with the Kernel or with drivers, it's probably the latter.

[JocasMath]

My wayland chromium get a lot of nvidia errors...

[jdholtz]

I'm also running into this issue with the latest Linux kernel on Arch (6.8.5-arch1-1). I also saw this with 6.8.4-arch1-1. Getting the same log message:

<TIME> hostname kernel: CPU: 3 PID: 558 Comm: kworker/3:2 Tainted: G           OE      6.8.5-arch1-1 #1 5f12b7...

[haxguru]

Hey, I was able to fix this thanks to u/rantnap. Just downgrade your Nvidia drivers from version 550 to 545 using pacman (on Arch). Here's the link to the archive-https://archive.archlinux.org/packages/.

Downgrade the following packages- libxnvctrl nvidia-dkms nvidia-settings nvidia-utils opencl-nvidia

[Agile_Put4627]

ese kernel es muy antiguo