Some kind of kernel panic

English Install/Boot/Login
1

Hello everyone,

I got the following kernel panic, when trying to boot:

Kernel Panic
Kernel Panic1920×1332 283 KB

I had to force the restart, but everything works. Does anyone is able to retrieve any information out of it? I have no knowledge about it.

From what I could find:
Ooops: general protection fault, probably for non-canonical address, could be related to RAM problems, so I’ll have to test my RAM.

I am able to boot normally again now, and everything works as always. How do you handle these situations? Just ignore if it happens once? Try to debug?

Sorry, there was sun and I was not home and couldn’t move (I was in a coffee shop).

My main question is:
How seriously should I take these?

I already had some before on other machines (when I was on Debian, mainly when booting from deep sleep and unencrypting).

This one happened after unencrypting the drive during my first boot.

2

What is visible shows the problem in btrfs driver. It could be permanent on-disk corruption, it could be run-time problem that went away after restart. It makes sense to boot any live medium with as recent as possible btrfsprogs and run btrfs check on this filesystem. And run memory test as well (not once, leave it running over night).

3

How do I do this? Is it possible to run it from a burned Leap/Tw/Aeon-USB?

For the memory test, I suppose running the latest Leap/Tumbleweed ISO from a USB and running a memtest from GRUB is the way to go?

Thank you, I will do that tomorrow then. Sadly I cannot do this today, since it is my only work laptop right now, and I still have to work tomorrow. I just made a backup, so I still am somewhat protected, if anything goes wrong…

4

Leap is too old, Tumbleweed should be fine, Aeon is just a Tumbleweed under the hood.

5

Many thanks! I know, I just wanted to make sure not to take the wrong one!

6

may i ask if you’re dual booting windows? similar thing happened to me when a windows update enabled fastboot in secret and disabling it in the windows terminal fixed it

7

Hello,no, I do not dual boot on this machine.

8

Hello, no, I do not dual boot on this machine.

9

Check BIOS settings for iGPU memory (RAM buffer) - set it to some constant value (1 - 2 GiB is OK). By default ‘RAM buffer’ = ‘dedicated RAM to iGPU’ is set to ‘auto’, that means dynamically allocate & change VRAM volume in RAM. This can cause surprises for Linux kernel.

Also try to reconnect (reset) memory modules if possible.

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.