[ On Mon, May 25, 1998 at 12:48:29 (-0700), Erik E. Fair wrote: ]
> Subject: panic: all bets are off...
>
> I just got this:
> 
> Memory error on CPU cycle!
>  ctx=1, vaddr=0xffe1590, paddr=0x834000
>  csr=d4<IPEND,IENA,CHK,ERR2>
> panic: all bets are off...
> 
> and it dropped into DDB.
> 
> What the heck is up with that?!

That was on your 3/60?

If so, then the good news is that it seems NetBSD is indeed trapping and
recognizing DRAM parity errors (if not, then what machine and what
memory config did it happen on?).

The bad news is it isn't yet decoding the address into the physical
device ID, so you'll have a harder time figuring out what SIMM to
replace....

-- 
							Greg A. Woods

+1 416 443-1734      VE3TCP      <gwoods@acm.org>      <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>