From: John Covici <covici@ccs.covici.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: my 5.15.93 kernel keeps rebooting
Date: Sun, 16 Apr 2023 06:28:47 -0400 [thread overview]
Message-ID: <m3wn2ci0io.wl-covici@ccs.covici.com> (raw)
In-Reply-To: <MW2PR07MB4058A806C39E2F69B25FA46CD2A09@MW2PR07MB4058.namprd07.prod.outlook.com>
On Thu, 16 Feb 2023 12:37:51 -0500,
Laurence Perkins wrote:
>
>
>
> >-----Original Message-----
> >From: John Covici <covici@ccs.covici.com>
> >Sent: Wednesday, February 15, 2023 7:20 AM
> >To: gentoo-user@lists.gentoo.org
> >Subject: Re: [gentoo-user] Re: my 5.15.93 kernel keeps rebooting
> >
> >On Wed, 15 Feb 2023 09:50:27 -0500,
> >Grant Edwards wrote:
> >>
> >> On 2023-02-14, Rich Freeman <rich0@gentoo.org> wrote:
> >>
> >> > Where are you getting this from, the system log/journal? This
> >> > doesn't seem like a clean shutdown, so if it is a kernel PANIC I
> >> > wouldn't expect the most critical info to be in the log (since it
> >> > will stop syncing to protect the filesystem). The details you need
> >> > probably will be displayed on the console briefly. You can also
> >> > enable a network console, which will send the dmesg output
> >> > continuously over UDP to another device. This won't be interrupted
> >> > by a PANIC unless there is some issue with the hardware or networking stack.
> >>
> >> If you've got a serial port[1], you could also set up serial logging.
> >> Though using serial ports have become a bit of a lost art, the serial
> >> console code in the kernel is pretty carefully designed to be the last
> >> man standing when things start to die. It's possible (though I
> >> wouldn't say probable) that a serial console will be able to show you
> >> stuff closer to the event horizon than a network console can.
> >>
> >> Anyway, since still I'm in the serial port business (yes, there are
> >> still plenty of people using serial ports in industrial settings) I
> >> had to mention it...
> >>
> >> [1] For this purpose you want a plain old UART on the motherboard type
> >> seial port. You'd be surprised how many motherboards still have
> >> them. Even though they're never brought out to a DB9 connector on
> >> the back panel, there's often an 8-pin header on the edge of the
> >> board somewhere, so you'd need one of these:
> >>
> >>
> >> https://www.amazon.com/C2G-27550-Adapter-Bracket-Motherboards/dp/B0002
> >> J27R8/
> >
> >I do have one which I use for my speech synthesizer. I also have one on my other box which I could hook up -- if I can find my null modem cable. I think I will try the netconsole first and the serial console if that does not work.
> >
> >Thanks for the hint.
> >
> >
> https://wiki.gentoo.org/wiki/Kernel_Crash_Dumps is another option if you're somehow not getting enough information out of the console. More complex to set up, but you can take an actual debugger to the result and hopefully find out exactly what's going on.
Second try, don't know what happened.
So, after not getting any results from net console and somehow my null
modem cable only seemed to work from another computer to the one with
the problem kernel, I am trying to figure out how to set up for
getting a crash dump.
When looking at the article, it seems to want a root partition -- I
use zfs, which automatically detects the root partition, so can I just
forget about that one?
Also I am using systemd, so there is no /etc/local.d, but I do have
another location where I put commands to run after everything else
has run -- do I put the start up script there?
Also, there is a file /etc/conf.d/kexec.conf and I got a notice to
move it to /etc/kexec.conf, what do I put there?
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
covici@ccs.covici.com
next prev parent reply other threads:[~2023-04-16 10:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 14:08 [gentoo-user] my 5.15.93 kernel keeps rebooting John Covici
2023-02-14 19:08 ` Rich Freeman
2023-02-14 19:54 ` John Covici
2023-02-14 21:25 ` Rich Freeman
2023-02-14 22:04 ` John Covici
2023-02-15 14:50 ` [gentoo-user] " Grant Edwards
2023-02-15 15:19 ` John Covici
2023-02-16 17:37 ` Laurence Perkins
2023-02-17 19:03 ` John Covici
2023-02-17 20:13 ` Mark Knecht
2023-02-17 21:30 ` John Covici
2023-04-16 10:09 ` John Covici
2023-04-16 10:28 ` John Covici [this message]
2023-02-15 16:42 ` Grant Edwards
2023-02-16 11:50 ` John Covici
2023-02-16 12:11 ` Rich Freeman
2023-02-16 14:08 ` John Covici
2023-02-16 14:17 ` Mark Knecht
2023-02-16 14:33 ` Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wn2ci0io.wl-covici@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox