(This is all re: a sparc64 machine running NetBSD 4.0_RC1, using
a RAIDframe RAID1...)

On Sep 20, 2007, at 12:29, Chris Ross wrote:
>   I still need to get the machine to crash-dump at all, so.  :-)

   Okay, now I have a machine with a kernel that's configured:

config netbsd root on raid0 type ? dumps on sd0

   But, I'm still seeing:

login: [halt sent]
cpu0: kdb breakpoint at 1297e20
Stopped at      netbsd:cpu_Debugger+0x4:        nop
db> sync
syncing disks... panic: switch wchan
cpu0: kdb breakpoint at 1297e20
Stopped at      netbsd:cpu_Debugger+0x4:        nop
db> reboot 0x100
Frame pointer is at 0xe0014e61
Call traceback:
128def0(1, d, 0, 1848400, e00159e0, 0, e0014f31) fp = e0014f31
10a17c0(100, 0, 185149c, 1851400, 1851490, 185146c, e0014ff1) fp =  
e0014ff1
10a1240(e0015a98, 0, 1, e0015978, 72, 72000000, e00150c1) fp = e00150c1
10a16b4(180c128, 1320530, 0, 0, e0015b88, b, e0015211) fp = e0015211
10a4cdc(1297e28, 0, 15ad9c00, 140e04800, e00165d800, 0, e0015301) fp  
= e0015301
12991a0(0, 0, 0, 0, ffff, 1000000, e00153d1) fp = e00153d1
1296c98(101, e0016350, 0, 11, e0016508, 188cc00, e0015931) fp = e0015931
1008b34(e0016350, 101, 1297e20, 1d0006, 0, 1, e0015aa1) fp = e0015aa1
11e3a6c(140e048, e00165d8, 0, 0, 0, a, e0015c81) fp = e0015c81
1009fa4(18055aa, 104, 2, 0, 180c000, 1885f90, e0015d51) fp = e0015d51
11d01a8(18852a0, 0, 50, 1814e10, 186a000, 1882800, e0015e01) fp =  
e0015e01
11d0378(18852a0, 0, 98b429ba8, a, 186a000, 1882800, e0015ed1) fp =  
e0015ed1
121b02c(18852a0, e0016a7c, 10, 1885010, 1008a520, a, e0015f91) fp =  
e0015f91
1218de8(170c9a00, 0, 7fffffffffffe000, 18852a0, 11, 1805400,  
e00161f1) fp = e00161f1

dump to dev 7,1 not possible
rebooting

   When I try to crash-dump the machine.    Why is it not able to dump?
Does that message have something to do with the first panic that came
up with "sync" ?

   Thanks.  Any help appriciated...

                      - Chris