| >>>>> "eeh" == eeh  <eeh@netbsd.org> writes:
|     eeh> Try booting with -V.  Also do a `.trap-registers'.
|
| ok boot net netbsd.gz -V -v
| Boot device: /sbus/SUNW,hme@e,8c00000  File and args: netbsd.gz -V -v
| 15800 >> NetBSD/sparc64 OpenFirmware Boot, Revision 
| >> (chs@ultra2, Sun Dec 23 01:59:35 PST 2001)
| Using BOOTPARAMS protocol: ip address: 192.168.171.10, hostname: tidy
| root addr=192.168.171.1 path=/usr/src/tidy/root
| loadfile: reading header
| elf64_exec: Booting /sbus@1f,0/SUNW,hme@e,8c00000/netbsd.gz
| 4803384@0x1000000+135096@0x1800000+4059208@0x1820fb8 
| symbols @ 0xfff04300 74+324096+173216 start=0x1000000
| chain: calling OF_chain(800000, eef0, 1000000, fffb1a80, 18)
| [ using 498160 bytes of netbsd ELF symbol table ]
| Fast Data Access MMU Miss                        
| ok .trap-registers
| %TL:1 %TT:68 %TPC:1009ba8 %TnPC:1009bac 
| %TSTATE:82000405  %CWP:5 
|    %PSTATE:4 AG:0 IE:0 PRIV:1 AM:0 PEF:0 RED:0 MM:0 TLE:0 CLE:0 MG:0 IG:0 
|    %ASI:82  %CCR:0  XCC:nzvc   ICC:nzvc

| Suggestions?

It died trying to fire up the first CPU, where it traverses the linked
list of cpuinfo structures to looking for a structure that matches the
CPU's UPAID.

So I'd suggest looking at the properties on each of the cpu nodes to
see what the upa-portid properties are on each of them.

Also, firing up solaris and getting the output of `prtconf -pv' might
give some other insights into how that machine is put together.

Eduardo