Page MenuHomeNawan HQ

A kernel panic occurs when an offline system update is in progress
Stalled, LowPublic

Description

Today, when I was about to shut down my laptop, I received a confirmation that a system update had been downloaded and was ready to be installed upon rebooting. I chose to install the update and clicked the Shutdown button. However, after a few minutes, the progress bar got stuck at 50%, and the CapsLk indicator start blinking which indicate kernel panic.

To diagnose a panic, a feature called kdump is available which uses a second Linux kernel running in a reserved region of memory to save a core dump of the failed kernel for analysis. https://unix.stackexchange.com/questions/3840/the-caps-lock-and-scroll-lock-lights-are-flashing-and-everything-is-frozen

Event Timeline

nawan triaged this task as Unbreak Now! priority.
nawan changed the task status from Open to In Progress.Sat, May 16, 20:45
nawan moved this task from Inbox to Doing on the User-nawan board.

I cant get kernel coredump but I get this from journalctl -b -1 -r:

Mei 16 19:25:50 IdeaPad-3-14IGL05 systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables.
Mei 16 19:25:50 IdeaPad-3-14IGL05 systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
Mei 16 19:25:50 IdeaPad-3-14IGL05 systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
Mei 16 19:25:50 IdeaPad-3-14IGL05 systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files...
Mei 16 19:25:50 IdeaPad-3-14IGL05 systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage...
Mei 16 19:25:50 IdeaPad-3-14IGL05 systemd-sysctl[288]: Couldn't write '1100' to 'vm/swappiness': Invalid argument
nawan changed the task status from In Progress to Stalled.Sat, May 16, 20:57
nawan lowered the priority of this task from Unbreak Now! to Low.
nawan moved this task from Doing to On Hold on the User-nawan board.

For now, I have set the correct swappiness value to 110 and run fsck, as I have to perform a hard reboot when a kernel panic occurs. Change the priority of this task to low until I can ensure that this won't happen again.

I just got a kernel panic again. This time, it happened while booting the OS, not during a system update and I had to hard reboot. Also I forgot to install kdump-tools and enable kdump, so this time I'm going to do that.

$ kdump-config status
current state   : ready to kdump