linux-mips
[Top] [All Lists]

Re: MC Parity Error

To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: MC Parity Error
From: Ralf Baechle <ralf@linux-mips.org>
Date: Fri, 23 Apr 2004 18:45:17 +0200
Cc: Florian Lohoff <flo@rfc822.org>, linux-mips@linux-mips.org
In-reply-to: <Pine.LNX.4.55.0404231509190.14494@jurand.ds.pg.gda.pl>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20040423080247.GC5814@paradigm.rfc822.org> <Pine.LNX.4.55.0404231509190.14494@jurand.ds.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Fri, Apr 23, 2004 at 03:11:19PM +0200, Maciej W. Rozycki wrote:

> > success report for the MC Bus Error handler :)
> > 
> > Apr 19 23:17:32 resume kernel: MC Bus Error
> > Apr 19 23:17:32 resume kernel: CPU error 0x380<RD PAR > @ 0x0f4c6308
> > Apr 19 23:17:32 resume kernel: Instruction bus error, epc == 2accf310, ra 
> > == 2accf2c8
> > 
> > I guess i have bad memory. The interesting point is that the machine
> > continued to run for another 2 days. Shouldnt a memory error halt the
> > machine ?
> 
>  As it happened in the user mode, I'd expect only the victim process to be
> killed.

The KSU bits are meaningless.  On Indy like most other MIPS systems a
bus error exception may be delayed.  So the generic solution requires
tracking down the actual user, something which in the current kernel is
relativly easy due to rmap.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>