| A non-netboot gets somewhat farther:
| ok boot disk:b netbsd -s
| Boot device: /pci@1f,4000/scsi@3/disk@0,0:b  File and args: netbsd -s
| NetBSD IEEE 1275 Bootblock
| ..>> NetBSD/sparc64 OpenFirmware Boot, Revision 1.4
| >> (mrg@powerofseven.eterna.com.au, Wed Aug 22 07:27:23 EST 2001)
| loadfile: reading header
| elf64_exec: Booting /pci@1f,4000/scsi@3/disk@0,0:b/netbsd
| 4516312@0x1000000+148632@0x1800000+4045672@0x1824498
| symbols @ 0xfef90300 74+298728+157356 start=0x1000000
| chain: calling OF_chain(800000, ee10, 1000000, fff83a80, 18)
| [ using 456936 bytes of netbsd ELF symbol table ]
| pmap_bootstrap: could not claim physical dseg extension at a6ca0000
| size 360000
| Setting DTLB entry 00000000 01000000 data e0000000 a7400074
| Setting DTLB entry 00000000 01800000 data e0000000 a6400076
| Setting ITLB entry 00000000 01000000 data e0000000 a7400074
| Setting CPUINFO mappings...
| Setting TSB pointer 00000000 018b0000
| consinit()
| setting up stdin
|
| SIR Reset
|
| Watchdog Reset
| Externally Initiated Reset
|
| And in case these trap registers are useful:
| %TL:1 %TT:1ff %TPC:0 %TnPC:0
| %TSTATE:0  %CWP:0
|    %PSTATE:0 AG:0 IE:0 PRIV:0 AM:0 PEF:0 RED:0 MM:0 TLE:0 CLE:0 MG:0 IG:0
|    %ASI:0  %CCR:0  XCC:nzvc   ICC:nzvc
|
| %TL:2 %TT:68 %TPC:f000a15c %TnPC:f000a160
| %TSTATE:4482000402  %CWP:2
|    %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:44  XCC:nZvc   ICC:nZvc

Looks like you took a MMU miss fault in the firmware...

|
| %TL:3 %TT:32 %TPC:1008590 %TnPC:10085a0
| %TSTATE:4482041402  %CWP:2
|    %PSTATE:414 AG:0 IE:0 PRIV:1 AM:0 PEF:1 RED:0 MM:0 TLE:0 CLE:0
|    MG:1 IG:0
|    %ASI:82  %CCR:44  XCC:nZvc   ICC:nZvc

Which then generated a bus fault, which shouldn't happen here...

| %TL:4 %TT:4 %TPC:100867c %TnPC:1008680
| %TSTATE:4482001502  %CWP:2
|    %PSTATE:15 AG:1 IE:0 PRIV:1 AM:0 PEF:1 RED:0 MM:0 TLE:0 CLE:0 MG:0 IG:0
|    %ASI:82  %CCR:44  XCC:nZvc   ICC:nZvc

So it generated a software initiated reset.

It would be interesting to find out what code was being executed in the kernel
that caused the problem....

Eduardo