On Wed, 15 Feb 2023 09:50:27 -0500,
Grant Edwards wrote:
>
> On 2023-02-14, Rich Freeman <ri...@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/B0002J27R8/
>
>
Still having problems with the netconsole -- I am determined to get
this working,so let me explain a bit more.
The sending computer has two nics, eno1 for the internal network and
eno2 is on the internet. So, my netconsole stanza said
netconsole=@192.168.0.1/eno1,@192.168.0.2
The box which is at 192.168.0.2 has netcat (windows version) and I
tried the following:
netcat -u -v -l 192.168.0.2 6666 and I also tried 192.168.0.1 6666
which is the ip address of the linux console which I am trying to
debug.
I also tried 0.0.0.0 6666 which did not work either, but I think the
windows firewall was blocking, and I did fix that, but did not try the
0.0.0.0 after that.
So, what am I doing wrong here?
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
cov...@ccs.covici.com
