You are not logged in.
Last night my firewall, which has been running flawlessly for several years, crashed. I powered it back on, poked around the journal a bit, but didn't see any indication of the cause. I left `journalctl -f` running in an SSH session. It crashed again within an hour. At that point I was reminded that I had updated and rebooted earlier in the evening. Since then it has crashed about a dozen times, usually after 20-25 minutes.
I noticed a few things. It never prints an error, stack trace, core dump message, or anything when it dies. The keyboard becomes completely unresponsive; caps lock doesn't toggle the LED, and the magic SysRq keys don't work. Based on my experience, that indicates a hard lock in the kernel itself, as opposed to anything that the kernel might notice and log before crashing.
I was hoping to find a newer kernel "fix", so I ran `pacman -Syu` and was able to upgrade a few packages this evening; the kernel was not among them, unfortunately, but systemd was. I rebooted, but it crashed again after about 25 minutes.
Finally I installed the previous kernel packages (originally installed on Nov 23) from /var/cache and it is up and running `6.5.11-hardened1-1-hardened` now, for about 45 minutes. Keeping my fingers crossed!
Has anybody else had problems with `linux-hardened-6.5.13.hardened1-1`?
--
M Hill (mhill8)
Offline
Offline