On Sat, 11 Apr 1998, Matthew N. Dodd wrote:
> On Sat, 11 Apr 1998, der Mouse wrote:
> > Is there anything I can do to help improve NetBSD's behavior in this
> > circumstance?  I have a known-bad SIMM I can swap into any socket
> > desired. :-)  Or has something already been done, and I just need to
> > run a more current version to get proper memory error reporting?
> 
> I had a known bad SIMM and ferreted it out by repeated use of the PROM
> monitor memory test function.  It also prints the slot #.

Replying to myself here but I wasn't quite clear with my reply.

Clearly the PROM knows how to identify the location of a physical SIMM as
its mapped into the memory address range.  Digging through Forth to find
out how isn't all that appealing I admit but the info is probably there.

/* 
   Matthew N. Dodd		| A memory retaining a love you had for life	
   winter@jurai.net		| As cruel as it seems nothing ever seems to
   http://www.jurai.net/~winter | go right - FLA M 3.1:53	
*/