Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Florian Lohoff <flo@rfc822.org>, linux-mips@linux-mips.org
Subject: Re: MC Parity Error
Date: Fri, 23 Apr 2004 18:45:17 +0200	[thread overview]
Message-ID: <20040423164517.GA16401@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0404231509190.14494@jurand.ds.pg.gda.pl>

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

  reply	other threads:[~2004-04-23 16:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23  8:02 MC Parity Error Florian Lohoff
2004-04-23 13:11 ` Maciej W. Rozycki
2004-04-23 16:45   ` Ralf Baechle [this message]
2004-04-23 17:11     ` Maciej W. Rozycki
2004-04-23 20:43       ` Dominic Sweetman
2004-04-23 21:06         ` Maciej W. Rozycki
2004-04-24  6:28       ` 32-bit ABI Stanislaw Skowronek
2004-04-24  7:09         ` Thiemo Seufer
2004-04-24  7:17         ` Ralf Baechle
2004-04-24  7:31           ` Stanislaw Skowronek
2004-04-24  7:38             ` Ralf Baechle
2004-04-24  7:46               ` Stanislaw Skowronek
2004-04-24  7:51                 ` Maciej W. Rozycki
2004-04-24  7:55                   ` Ralf Baechle
2004-04-24  8:07                     ` Maciej W. Rozycki
2004-04-24  8:14                       ` Stanislaw Skowronek
2004-04-24  8:18                       ` Ralf Baechle
2004-04-24  8:23                         ` Maciej W. Rozycki
2004-04-24  8:26                           ` Ralf Baechle
2004-04-24  8:49                             ` Maciej W. Rozycki
2004-04-24  8:14                 ` Ralf Baechle
2004-04-24  8:17                   ` Stanislaw Skowronek
2004-04-24  8:26                     ` Thiemo Seufer
2004-04-24  7:37           ` Thiemo Seufer
2004-04-24  7:18         ` Maciej W. Rozycki
2004-04-24  7:34           ` Stanislaw Skowronek
2004-04-24  7:44             ` Ralf Baechle
2004-04-24  7:47               ` Stanislaw Skowronek
2004-04-24  7:48             ` Maciej W. Rozycki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040423164517.GA16401@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=flo@rfc822.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@ds2.pg.gda.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox