On Thu, 12 Oct 2023 at 11:09, D. Hugh Redelmeier via talk <[email protected]> wrote: > | From: Giles Orr via talk <[email protected]> > > | 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). > > | I'm not great at debugging Linux crashes. The `dmesg` command is > | useless, as it only shows the log since the last boot. > > I think that everything in dmesg goes to the Journal. > > Have you compared journal entries from just before each crash to see if > there is a common theme? > > Good luck!
Thanks to BCLUG for `journalctl --boot -1` (and I assume `-2` etc.). That's a blessing. I ended up running `systemctl disable cups.service cups.socket cups.path` and `systemctl stop cups.service cups.socket cups.path` - so more or less what you were trying to suggest. :-) The system didn't crash yesterday, so that's good. Hugh seems to be correct: I think everything in `dmesg` ends up in the journal. But what I find interesting is that not everything in /var/log/systemlog is in the journal. I was comparing the systemlog entries, and that's how I concluded CUPS/printer drivers were the problem. The loading of those modules weren't mentioned in the journal. In this case, it seems that the information I most needed (ie. "this is a printer driver problem") came from syslog. This is a negative test case - ie. I don't know it's solved, and won't ever be certain. Unless it crashes again, then I know it's not solved. Ugh. Thanks everyone. -- Giles https://www.gilesorr.com/ [email protected] --- Post to this mailing list [email protected] Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
