Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Clausen <clausen@melbourne.sgi.com>
Cc: Jason Ormes <jormes@wideopenwest.com>, linux-mips@linux-mips.org
Subject: Re: kernel boot error.
Date: Wed, 5 Feb 2003 17:48:07 +0100	[thread overview]
Message-ID: <20030205174807.B13033@linux-mips.org> (raw)
In-Reply-To: <20030205004345.GI27302@pureza.melbourne.sgi.com>; from clausen@melbourne.sgi.com on Wed, Feb 05, 2003 at 11:43:45AM +1100

On Wed, Feb 05, 2003 at 11:43:45AM +1100, Andrew Clausen wrote:

> On Tue, Feb 04, 2003 at 06:41:10PM -0600, Jason Ormes wrote:
> > hello,
> > 
> > can someone help me with this error?  Is this because the network failed?
> 
> I'm getting exactly the same problem.  What machine are you using?
> I'm using an ip27 (origin 200), and an acenic network card.
> 
> It seems that there all kinds of PCI hacks in the ip27 support,
> and I'm currently trying to figure out how to get this card working...

His particular machine is a uniprocessor machine, a very rare configuration.
In all the years I'm working with Origins this is just the second I
encounter.  Note that disabling one of the processor doesn't suffice;
this problem really only seems to hit machines with one physical processor.

  Ralf

  parent reply	other threads:[~2003-02-05 16:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05  0:41 kernel boot error Jason Ormes
2003-02-05  0:43 ` Andrew Clausen
2003-02-05  1:12   ` Jason Ormes
2003-02-05  1:14     ` Andrew Clausen
2003-02-05  1:37   ` Tibor Polgar
2003-02-05  3:06     ` Andrew Clausen
2003-02-05 14:03       ` Ralf Baechle
2003-02-06  0:34         ` Andrew Clausen
2003-02-05 16:48   ` Ralf Baechle [this message]
     [not found] <ralf@linux-mips.org>
2003-02-05 17:07 ` Tor Arntsen
2003-02-06 11:25   ` Ralf Baechle

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=20030205174807.B13033@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=clausen@melbourne.sgi.com \
    --cc=jormes@wideopenwest.com \
    --cc=linux-mips@linux-mips.org \
    /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