ok boot disk0 /ofwboot /netbsd -a

Hm. didn't know you could pass two args...

	Fast Data Access MMU Miss
	ok .trap-registers
	%TL:1 %TT:68 %TPC:f00287a4 %TnPC:f00287a8 
	%TSTATE:9900000406  %CWP:6 
	   %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:0  %CCR:99  XCC:NzvC   ICC:NzvC

	%TL:2 %TT:68 %TPC:f0053e80 %TnPC:f0053e84 
	%TSTATE:858041406  %CWP:6 
	   %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:58  %CCR:8  XCC:nzvc   ICC:Nzvc

	%TL:3 %TT:68 %TPC:f0053f74 %TnPC:f0053f78 
	%TSTATE:8058041400  %CWP:0 
	   %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:58  %CCR:80  XCC:Nzvc   ICC:nzvc

Those are all PROM addresses.

You need to disassemble the TPC addresses to find out
what register it was using when it faulted.  Also,
you can try `ctrace' or `<n> .window' to determine
where it jumped in to the firmware.  Then dump
the argument in %o0 to find out what command was
being executed.

Eduardo