Question

26

Where are kernel panic logs?

rated 0 times [ 26] [ 0] / answers: 1 / hits: 133029 / 1 Year ago, sat, may 20, 2023, 8:00:49

I've got problem with Handbrake/ffmpeg. After ~5 minutes transcoding, the computer locks up. I'm fairly sure it's a kernel panic because caps-lock starts flashing.

There are a few logical questions about what to do and some about specific bugs but I'm really after one thing: what happened right before everything died?!

I've checked /var/log/kern.log and all I see around the time is me sticking in a DVD and then a few minutes later, the system booting up. No errors, no panic notice.

Is there any way to force panics to be logged? I'm fairly sure I can reproduce this (it's happened 100% of the times I've tried recently) so while I'd rather this "just worked", I'm happy enough to reboot a few times if it means I can find the cause of the panic.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

rstride

Add To Favorites

Follow

Total Points: 305

Total Questions: 112

Total Answers: 118

Location: Mali

Member since Sat, Dec 26, 2020

3 Years ago

rstride questions

1 How can I downmix stereo audio output to mono in PipeWire (on 22.10)?

Thu, Sep 22, 22, 12:37, 2 Years ago

1 Ubuntu 22.04.1 LTS Bluetooth not working, default adapter not found

Sat, Jul 23, 22, 12:51, 2 Years ago

1 HDMI port not working with Ubuntu

Fri, Feb 10, 23, 12:32, 1 Year ago

1 Ubuntu 20.04: No WiFi Adapter found due to Microcode SW error detected, iwlwifi error code 5

Wed, Oct 13, 21, 06:56, 3 Years ago

1 When I turn off Ubuntu, it shows black screen but it doesn't power off

Sun, Dec 4, 22, 19:59, 1 Year ago

View All

answered 1 Year ago ongdiligenc · Accepted Answer

All your system logs in Ubuntu are handled by rsyslog which keeps its configuration in /etc/rsyslog.conf and /etc/rsyslog.d/.

For more information on how to configure rsyslog and the possible options visit the rsyslog.conf man page.

Opening /etc/rsyslog.d/50-default.conf you can see that one of the lines contains

*.*;auth,authpriv.none -/var/log/syslog*

Meaning that the file you are looking for in this case is any of the huge /var/log/syslog logs you will probably have.

You can see that the file name also starts with a -, this means that the file is cached before writing, its great but can leave you with a bad log, what you want is that the log is written as soon as there is a problem.
Remove the dash and reboot or reload rsyslog and then make your computer crash again, check /var/log/syslog.