On Sun May28'23 12:41:54PM, Samuel Sieb wrote: > From: Samuel Sieb <samuel@xxxxxxxx> > Date: Sun, 28 May 2023 12:41:54 -0700 > To: users@xxxxxxxxxxxxxxxxxxxxxxx > Reply-To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > Subject: Re: kernel watchdog BUG > > On 5/28/23 09:15, stan via users wrote: > > On Sun, 28 May 2023 09:52:04 -0500 > > Ranjan Maitra <mlmaitra@xxxxxxx> wrote: > > > I rebooted in the good old ways of some other OSs, and the problem > > > has not reared again for now. I did look at /var/log/messages but > > > found nothing on kernel lockup. Are these some other log files I > > > should be looking at. > > > > journalctl is the official message repository now. I like to use > > journalctl -r > > because that reverses it, so I am searching from now into the past. > > You could try a > > /soft lockup > > and see if you get any hits. > > You'll want to add "-b -1" as well, so you start with the logs from the > previous boot, not the current one. > > "journalctl -b -1 -r" Thanks! It is possible I do not have this set up because I get: $ sudo journalctl -b -1 -r /soft lockup Specifying boot ID or boot offset has no effect, no persistent journal was found. Best wishes, Ranjan _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
