Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Michael Hill <mike@mdhill.interlog.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Uploads ...
Date: Wed, 10 Dec 1997 04:02:10 +0100	[thread overview]
Message-ID: <19971210040210.27443@uni-koblenz.de> (raw)
In-Reply-To: <9712091934.ZM3116@mdhill.interlog.com>; from Michael Hill on Tue, Dec 09, 1997 at 07:34:21PM -0500

On Tue, Dec 09, 1997 at 07:34:21PM -0500, Michael Hill wrote:

> Thanks for the kernel binary.  Unfortunately it quits in the same spot as the
> previous kernel I tried (the R4600 V2.0 problem).  You said you had a stable
> kernel on the SNI RM200.  This time I used the Indy kernel; should I try the
> rm200 kernel?

If your have a RM200 ...

Is it still that bus error message you get?  If so, could you please mail
me the register dump displayed on the screen.

>  If I were to get my Indy back on support would they replace the
> CPU because of this?

No, because that problem can be handled in the OS software and > 2.1.57 do
so.

  Ralf

  reply	other threads:[~1997-12-10  3:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-08 14:06 Uploads Ralf Baechle
1997-12-08 14:58 ` Uploads Alan Cox
1997-12-08 14:58   ` Uploads Alan Cox
1997-12-08 15:12   ` Uploads Ralf Baechle
1997-12-09  6:03 ` Uploads Alex deVries
1997-12-09  7:42   ` Uploads ralf
1997-12-10  0:34 ` Uploads Michael Hill
1997-12-10  3:02   ` ralf [this message]
1997-12-11 22:03     ` Uploads Benjamin Pannier
1997-12-12  1:42       ` Uploads ralf
     [not found]     ` <9712110612.ZM1219@mdhill.interlog.com>
1997-12-12  2:34       ` Indy crash during bootup ralf
1997-12-12  3:15         ` William J. Earl
1997-12-12  3:42           ` ralf
1997-12-12 10:04         ` Benjamin Pannier

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=19971210040210.27443@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=mike@mdhill.interlog.com \
    /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