Define crashing :) Is is simply rebooting or freezing or shuting down. I would try to use journalctl to check logs; as detailed in the keyboard thread. Normally the kernel should trace the oops/fault before crashing. An alternative would be to boot an older kernel - it should be still installed - and see if that is stable. On 11/10/2023 18:30, Giles Orr via talk wrote:
I have a Debian 12 system that's my daily driver. In the last two days, it crashed twice when I was away from the keyboard and nothing was happening (around the same time of day now that I think about it). The system has previously been very stable, usually up for a month at a time with reboots only to pick up new kernels. I should note that when I turned it on and ran upgrades on Monday after a week away, it upgraded a lot of packages for Debian release 12.2.
I'm not great at debugging Linux crashes. The `dmesg` command is useless, as it only shows the log since the last boot. So I turned to /var/log/syslog. What I noticed was this, the only line of consequence about a millisecond before the reboot:
2023-10-10T11:36:23.839046-04:00 sli7d systemd-modules-load[399]: Inserted module 'lp'
I don't have a printer, and I hadn't just done a "print-to-PDF" or anything like that - the machine had been idle for a couple hours. This morning it crashed again, and milliseconds before the crash I found these (again, the machine was idle when this happened):
2023-10-11T12:20:54.647048-04:00 sli7d systemd-modules-load[382]: Inserted module 'lp' 2023-10-11T12:20:54.647254-04:00 sli7d systemd-modules-load[382]: Inserted module 'ppdev' 2023-10-11T12:20:54.647280-04:00 sli7d systemd-modules-load[382]: Inserted module 'parport_pc' 2023-10-11T12:20:54.647290-04:00 sli7d lvm[372]: 3 logical volume(s) in volume group "primary" monitored 2023-10-11T12:20:54.647302-04:00 sli7d systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage... 2023-10-11T12:20:54.647312-04:00 sli7d systemd-udevd[398]: Using default interface naming scheme 'v252'.
I just ran `apt full-upgrade` (right now) and watched it upgrade Samba. Is it possible that Samba was triggering "lp"-related stuff which was causing the crash? Although why it would cause a crash I don't know. No new kernel (and thus no new modules). I suppose I could reboot and select and older kernel and see if that was stable ...
Suggestions on how to better debug this would be most welcome. Does blacklisting the "lp" module sound like a good idea? Any other ideas?
Re-installing would be ... unpleasant. This is my primary machine and heavily tweaked-up. But I guess I'll do that if I have to. Keeping it as a last resort though (daily crashes would get me there!).
-- -- This email has been checked for viruses by Avast antivirus software. www.avast.com