this post was submitted on 12 Jan 2026
10 points (81.2% liked)

Linux

16497 readers
163 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
MigratingtoLemmy@lemmy.world
10
Finding out crash logs? (lemmy.today)
submitted 1 month ago by kajees@lemmy.today to c/linux@lemmy.world
8 comments fedilink hide all child comments
 

I’ve recently installed Mint on a clean partition, and set up dual booting to always prefer that partition over the Win10 one (on a separate sdd). At the moment I’m trying Mint for the very first time, seeing how I like it. And truth be told, it’s quite good! However I’ve had 2 system crashes in the last 2 days, and some games crash without an error log (old world went straight to desktop while mid-turn, and ghost of Tsushima crashed after I paused the game when pressing start).

I’d love to be more knowledgeable and figure this out by myself, but I can’t find a starting point to determine what went wrong in any of these instances.

Are there execution logs or actual error logs that I can check somewhere?

you are viewing a single comment's thread
view the rest of the comments
[–] who@feddit.org 1 points 1 month ago* (last edited 1 month ago) (1 children)

I think Mint uses systemd, so after rebooting, you should be able to review the system log from the previous boot with this command:

journalctl --boot=-1

The kernel might still be running even when the display is frozen. If that's the case, you can try rebooting more gently than a forced power-off would do. While holding down the Alt key, type these keys in order, with a couple seconds between each tap: SysRq R E I S U B

https://en.wikipedia.org/wiki/Magic_SysRq_key

Note: SysRq is disabled by default on some distros, and unsupported by some keyboard controllers. You can check (when the system is not frozen) by holding Alt and typing SysRq H while watching the output of sudo dmesg --follow. If it's working, you should see a help message.

For what it's worth, what you're describing sounds like it might be a GPU driver misbehaving, perhaps in response to power saving events. If you have an Nvidia card, you might try a different driver version. Otherwise, you might try an older or newer kernel version.

[–] kajees@lemmy.today 1 points 1 month ago

This is extremely helpful, thanks! Gpu is amd, as is the motherboard. I’ll be on the lookout for the next time the system freezes.