Re: Saving kernel crash dumps

[Sad Clouds <cryintothebluesky%gmail.com@localhost>]

On Wed, 08 Oct 2025 05:23:19 +1100
matthew green <mrg%eterna23.net@localhost> wrote:

> it's actually better for KGDB if it is *not* also sharing
> the console.  my old setup was ttya as console and ttyb
> for kgdb.  then you don't have to do anything for sharing..
> 
> 
> .mrg.

OK I figured out how to get the serial console running (just log into
ILOM once via serial MGM port, run "start /SP/console" and then use another
ssh session to log into ILOM and from there start/stop system, etc).
I can then drop out of the serial console with ~~. (~ extra for ssh
escape) and reconnect again with cu or gdb.

I'm confused about these options:

options 	KGDB		# remote debugger
options 	KGDB_DEVNAME="\"com\"",KGDB_DEVADDR=0x3f8,KGDB_DEVRATE=9600
makeoptions	DEBUG="-g"	# compile full symbol table

Do I need both KGDB_DEVNAME and KGDB_DEVADDR or is the devname
sufficient? And what do I put for the devname?

On T5220 NetBSD shows this:

[     1.000000] com0 at ebus0 addr ca0000-ca0007 ipl 13: ns16550a, 16-byte FIFO

So KGDB_DEVADDR is probably 0xca0000? And how do I figure out which
device com0 maps to on this machine?

The first boot messages are:

Loading netbsd: 13607208+515040+429128 [800280+515929]=0xf286c8
[   1.0000000] Loaded initial symtab at 0x1ce7150, strtab at 0x1daa768, # entries 31587
consinit()
stdin node = f0285768
stdout package = f0285768
buffer @ 0x2009cb8
console is /virtual-devices@100/console@1