partial success. Got most of the way through the kernel
device attach. Got dumped into the debugger by a panic.
not familiar with netbsd kernel debugger. suggestions appreciated?

[much verboseness elided]
clock0 at ebus0 addr 0-1fff
clock0: device_register: bpname network()
: mk48t59: hostid ffffffff80cfd209       
flashprom at ebus0 addr 0-fffff addr 0-fffff not configured
SUNW,envctrltwo at ebus0 addr 600000-600003 ipl 40 ipl 37 not configured
hme1 at pci0 dev 1 function 1                                           
hme1: device_register: bpname network((null))
instance_match: pci device, want dev 0x1 fn 0x1 have dev 0x1 fn 0x1
        -- found ethernet controller hme1                          
: address 08:00:20:cf:d2:09              
nsphy0 at hme1 phy 1: DP83840 10/100 media interface, rev. 1
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
hme1: using vector 0 for interrupt                          
data memory error type 32 sfsr=0x0 sfva=0xfe037010 afsr=0x88000000 afva=0x1fe01000a00 tf=0xf1809100
panic: trap: memory error                                                                          
kdb breakpoint at 0xf126d168
Stopped in swapper at   cpu_Debugger+0x4:       nop
db>                                                


> On Fri, 25 Aug 2000, Mark Blackman wrote:
> 
> > > 
> > > I updated ftp.netbsd.org:/pub/NetBSD/arch/sparc64/other/netbsd.bootdebug
> > > with the E250 fix if anybody wants to test it out.
> > > 
> > > Eduardo Horvath				   
> > > 
> > using this kernel, I see more output but still seems to hit either
> > 'test' or 'test-method'. i.e... (pointer 'dump' at bottom). 
> 
> Oops, bug in the code.  That's what happens when you don't have the actual
> hardware to test on.  I just updated the file again.  Give it a
> try.  If it identifies your machine properly it should print out
> "prom_get_msgbuf: Cannot recover msgbuf on E250"
> 
> (Hope it works this time.)
> 
> Eduardo Horvath				   
>