> 1.2C (Mar08) plus Charles' new com driver.
> 
> Dropped into ddb with
> 
> kernel: non-maskable interrupt trap, code=0
> Stopped at	_pmap_pte+0x78: leave
> 
> I did a trace and then continued.  The machine kept running happily.
> I still have the trace on the console if anyone is intersted.
> 
> --sjg

I have a mainboard that usually gives me one of these when it is
first booted.  Under 95, it dies and says "memory parity error."
Mine seems like it occurs more readily if I'm accessing the network
immediately after booting, so I'm inclined to blame my ethernet
card or something.  I've replaced my SIMMs with brand new ones, and
the problem still occurs, so I'm fairly confident it is not actually
bad RAM.  Anyway, I don't believe this is a software problem.

-Andrew
-- 
-----------------------------------------------------------------
Andrew Gillham                            | This space left blank
gillham@whirlpool.com                     | inadvertently.
I speak for myself, not for my employer.  | Contact the publisher.