On Sun, 7 Nov 2004 15:42:52 -0500
Tim Kelly <hockey@dialectronics.com> wrote:

> 1) The install is RC2, but the MP kernel is RC4. Yes, I know this is
> not ideal, but I'm trying to build a compete userland to get up to
> date. 

Let me clarify this - I've tried repeatedly in the last two or three
days to get into releng.netbsd.org without success. I picked up the MP
kernel from
ftp://ftp.fr.netbsd.org/pub/NetBSD-daily/netbsd-2-0/200410160000/macppc/

which ended up being RC4. The earliest RC candidate I can see at
ftp.fr.netbsd.org is RC3. 

If consolidating is necessary before further debugging, should I get RC2
MP or do an upgrade to RC4 INSTALL?

Also, I was able to go back and get the chains from both panics:

mp_save_fpu_proc{1} pid = 19039.1, fpcpu->ci_cpuid = 0
panic: mp_save_fpu_proc
Stopped in pid 19039.1 (nbmake) at      netbsd:cpu_Debugger+0x10:      
lwz     r 0, r1, 0x14
db{1}> bt
0xd4151cd0: at panic+0x19c
0xd4151d60: at mp_save_fpu_lwp+0xec
0xd4151d80: at save_fpu_lwp+0x2c
0xd4151d90: at cpu_lwp_fork+0x184
0xd4151dd0: at uvm_lwp_fork+0x94
0xd4151e00: at newlwp+0x130
0xd4151e50: at fork1+0x3ac
0xd4151eb0: at sys___vfork14+0x30
0xd4151ed0: at syscall_plain+0xc8
0xd4151f40: user SC trap #282 by 0x418ab1a0: srr1=0xd032
            r1=0xffffdd50 cr=0x44000028 xer=0 ctr=0x418ab198


mp_save_fpu_proc{1} pid = 18943.1, fpcpu->ci_cpuid = 0
panic: mp_save_fpu_proc
Stopped in pid 18943.1 (make) at        netbsd:cpu_Debugger+0x10:      
lwz     r 0, r1, 0x14
db{1}> bt
0xd470fcd0: at panic+0x19c
0xd470fd60: at mp_save_fpu_lwp+0xec
0xd470fd80: at save_fpu_lwp+0x2c
0xd470fd90: at cpu_lwp_fork+0x184
0xd470fdd0: at uvm_lwp_fork+0x94
0xd470fe00: at newlwp+0x130
0xd470fe50: at fork1+0x3ac
0xd470feb0: at sys___vfork14+0x30
0xd470fed0: at syscall_plain+0xc8
0xd470ff40: user SC trap #282 by 0x418ab1a0: srr1=0xd032
            r1=0xffffcf20 cr=0x44000024 xer=0 ctr=0x418ab198

Other than r1, they appear identical to me.

thanks,
tim