I’m not sure what fixed it because I tried multiple things yesterday, but it shutdown normally last night.
Attempting to kill init means that something tried to kill PID 1. That’s… abnormal outside of a shutdown. But it can be normal during shutdown. So uhh… yeah: if it continues to be a problem then it needs to be reported and fixed by your distribution. What distribution are you using?
I see kernel panics at shutdown most often on Arch-based distros after updating system packages.
It sucks when it happens during shutdown but it’s typically not going to cause other problems… except perhaps not automatically booting if you wanted to reboot instead of shutdown.
I’m using the XFCE edition of Linux Mint. The Kernel updated yesterday morning, could that have something to do with it?
A kernel update, if it’s done right, shouldn’t cause a panic. But not every distro does updates right.
If you know the old version and the new version then it might be useful to reach out to the Mint community and see if they’re aware of issues like that.
https://linuxmint.com/getinvolved.php -> forums or chat might be fruitful to you
I see kernel panics at shutdown most often on Arch-based distros after updating system packages.
When I tried Arch, upgrading kernel would delete the kernel modules of the running kernel — somewhat unimpressive upgrade process.
As with everything in Arch, there’s a setting for that.
Personally I’d be worried there’s a transient disk issue. I’d ensure my backups are good and files aren’t being silently corrupted. I assume you’re on an NVME, they tend to fail instantly, but sometimes you’ll get transient file errors beforehand (like not being able to open a system library). Look at something like debsums to start with maybe.
I’m not having the issue anymore, I’m not sure what fixed it though as I tried multiple things yesterday.
Also, I’m not using an NVME, I’m actually just using an old laptop hard drive with one of those hard drive cases that basically converts it into an external hard drive.
That type of error is usually indicative of hdd issue. I only mentioned NVMEs because they tend to fail all at once, without recovery options. Spining disks usually fail slower (but not always). Take a peek at smart info, maybe run a scan. My guess is the cord got jostled though tbh
Like I said, I’m not having the issue anymore.
Also, I tried to check the smart info but the option is gray-out, is there something I need to do before I can check it?
Your libpcre seems broken. Reinstall the package that contains this file.
I did that yesterday and it might have fixed it because I didn’t have the issue but I did try multiple things yesterday, so I’m not sure.
Yes this is a kernel panic which occurs when something goes terribly wrong inside the system. This could be anything from broken software to defective hardware. You should observe if this happens regurlarly.
In addition to the other things mentioned, check the health of your drive. This could be a symptom of corruption.
I’d reinstall libpcre, looks like it’s gotten broken?
The kernel panic should be a direct result of shutdown (which I guess at this point is init/pid1) not finding its dependency and killing itself.
Could also be an SEU
That’s pretty specific, but I guess it’s possible.
Iirc it’s 1 bit per 500mb per week for your every day ram.
There’s this famous case where a speedrunner playing Mario had such a bit flip and affected his play time.
