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 #.

/*
   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	
*/