Subject: Re: 2.0 on indy fails
To: Manuel Bouyer <bouyer@antioche.eu.org>
From: Christopher SEKIYA <wileyc@rezrov.net>
List: port-sgimips
Date: 04/03/2004 20:30:20 
On Sat, Apr 03, 2004 at 11:28:00AM +0200, Manuel Bouyer wrote:

> CPU Parity Error Interrupt
> Local I/O interrupt register 2: 0x20 <DUART>
> CPU parity error register: 0x304<B2,MEM_PAR>
> CPU parity error: address: 0x8a8a210 <SIMM S2> 

That doesn't look good.

> Looks like a problem with a SIMM, isn't it ?

I concur.  Bad SIMM started generating bus errors, but the bus handler
wasn't hooked into the ISR ...

-- Chris
	GPG key FEB9DE7F (91AF 4534 4529 4BCC 31A5  938E 023E EEFB FEB9 DE7F)