I see a lot of these on my SS5 running 1.5.3_RC1:

(gdb) target kcore netbsd.17.core
panic: kernel fault
#0  mi_switch (p=0xf0206e18) at ../../../../kern/kern_synch.c:825
f825            cpu_switch(p);
(gdb) bt
#0  mi_switch (p=0xf0206e18) at ../../../../kern/kern_synch.c:825
#1  0xf0036328 in ltsleep (ident=0x0, priority=4,
    wmesg=0xf01a4580 "scheduler", timo=0, interlock=0x20000000)
    at ../../../../kern/kern_synch.c:482
#2  0xf0138930 in uvm_scheduler () at ../../../../uvm/uvm_glue.c:453
#3  0xf00272f0 in check_console (p=0xf0206800)
    at ../../../../kern/init_main.c:522
#4  0xf0007218 in cpu_hatch ()
can not access 0x3902fc, invalid address (3902fc)
can not access 0x3902fc, invalid address (3902fc)
can not access 0x3902fc, invalid address (3902fc)
can not access 0x3902fc, invalid address (3902fc)
can not access 0xefffffd8, invalid address (efffffd8)
can not access 0xefffffd8, invalid address (efffffd8)
Cannot access memory at address 0xefffffd8.
(gdb)

Is this a known problem? 

I'm not entirely sure this isn't a hardware problem, but the backtrace is
always the same. The machine doesn't have a keyboard or serial console
attached (on ttya); it has the console of another machine attached on ttyb
though. 


 - Hubert

-- 
Want to get a clue on IPv6 but don't know where to start? Try this:
* Basics -> http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.html
* Setup  -> http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html 
Of course with your #1 IPv6 ready operating system -> http://www.NetBSD.org/