this post was submitted on 06 Nov 2023
18 points (95.0% liked)
Linux
48363 readers
582 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
To this day I have no idea how to even get journalctl errors from exactly before that crash.
Like all this
journalctl -r -b 1
and all that doesnt seem to show the right ones.On my debian machine something like
journalctl -b 1 -k
shows stuff. There's also lots of debug files in /var/log/ like boot.log debug, kern.log, messages, syslog.But it somehow needs to be able to store the log on your disk. If the system craps out completely, it won't get written to disk. The magic SysRequest keys might help if it only freezes. I learned "Raising elephants is so utterly boring." You might wanna goggle that and learn how to do it.
Other than that, I mostly look at all logs (no '-b1' and search for the place where it rebooted. Sometimes you find other related stuff while scrolling. But my own (old) thinkpad doesn't ever crash.
I think there are other crash-dump tools available. It believe there's something called 'kdump-tools' available on Debian. YMMV.