Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Predrag Malicevic <pmalic@blic.net>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: O200 problem...
Date: Tue, 9 Jan 2001 00:41:38 -0200	[thread overview]
Message-ID: <20010109004138.A12181@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0101090210460.10752-100000@quake.blic.net>; from pmalic@blic.net on Tue, Jan 09, 2001 at 03:16:20AM +0100

On Tue, Jan 09, 2001 at 03:16:20AM +0100, Predrag Malicevic wrote:

> I'm trying to install Linux on an Origin 200 and I'm having problems with
> booting the kernel (CVS tree linux from oss.sgi.com).  I've included below
> a console session of my tries to boot the kernel.  In two cases below I
> used the default kernel configuration but without the SCSI driver.  In the
> first case I used parameters root=/dev/nfs and nfsroot=.... It reached
> 'Calibrating delay loop' and then 'Got dbe at 0xffffffff8013e970'.  After
> that, I guess, some kind of register dump followed (I'm working with MIPS
> architecture for the first time).  In the second case it reached "TCP:
> Hash tables configured". Besides these two tries, I've tried using
> different kernel configuration options in the machine selection category
> and besides the obvious ones (IP27, IP27 N-Mode and Multi-Processing), I'm
> clueless about the meaning of other options.

> CPU 0 clock is 65535MHz.

Something's fishy.  I guess ;-)

> [ Here the machines hangs again. I've tried many more times with different kernel configurations, but it's the same thing. It either "gets a dbe" or just stops after "TCP: Hash tables ..." ]

I assume it's your specific configuration that's triggering the problem.
I've got the current CVS kernel running on 2 dual processor O200 and a
32 processor Origin 2000, so it can't be all broken.  I think all known
to be working configuratons are machines with significantly more memory;
dunno if that's really related or not.

Thanks for sending the oops message; however without additional data
provided I can't use it.  Can you please point please put the kernel image
that resulted in the oops online?

  Ralf

WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@oss.sgi.com>
To: Predrag Malicevic <pmalic@blic.net>
Cc: linux-mips@oss.sgi.com
Subject: Re: O200 problem...
Date: Tue, 9 Jan 2001 00:41:38 -0200	[thread overview]
Message-ID: <20010109004138.A12181@bacchus.dhis.org> (raw)
Message-ID: <20010109024138.x8NFya7_K_W3OazCZ3z73UgmVVDD_la2h1rcNdteE4g@z> (raw)
In-Reply-To: <Pine.LNX.4.30.0101090210460.10752-100000@quake.blic.net>; from pmalic@blic.net on Tue, Jan 09, 2001 at 03:16:20AM +0100

On Tue, Jan 09, 2001 at 03:16:20AM +0100, Predrag Malicevic wrote:

> I'm trying to install Linux on an Origin 200 and I'm having problems with
> booting the kernel (CVS tree linux from oss.sgi.com).  I've included below
> a console session of my tries to boot the kernel.  In two cases below I
> used the default kernel configuration but without the SCSI driver.  In the
> first case I used parameters root=/dev/nfs and nfsroot=.... It reached
> 'Calibrating delay loop' and then 'Got dbe at 0xffffffff8013e970'.  After
> that, I guess, some kind of register dump followed (I'm working with MIPS
> architecture for the first time).  In the second case it reached "TCP:
> Hash tables configured". Besides these two tries, I've tried using
> different kernel configuration options in the machine selection category
> and besides the obvious ones (IP27, IP27 N-Mode and Multi-Processing), I'm
> clueless about the meaning of other options.

> CPU 0 clock is 65535MHz.

Something's fishy.  I guess ;-)

> [ Here the machines hangs again. I've tried many more times with different kernel configurations, but it's the same thing. It either "gets a dbe" or just stops after "TCP: Hash tables ..." ]

I assume it's your specific configuration that's triggering the problem.
I've got the current CVS kernel running on 2 dual processor O200 and a
32 processor Origin 2000, so it can't be all broken.  I think all known
to be working configuratons are machines with significantly more memory;
dunno if that's really related or not.

Thanks for sending the oops message; however without additional data
provided I can't use it.  Can you please point please put the kernel image
that resulted in the oops online?

  Ralf

  parent reply	other threads:[~2001-01-09  2:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09  2:16 O200 problem Predrag Malicevic
2001-01-09  2:16 ` Predrag Malicevic
2001-01-09  2:41 ` Ralf Baechle [this message]
2001-01-09  2:41   ` Ralf Baechle
2001-01-09 10:23   ` Predrag Malicevic
2001-01-09 10:23     ` Predrag Malicevic
2001-01-12 14:20   ` Predrag Malicevic
2001-01-12 14:20     ` Predrag Malicevic
2001-01-16  6:10     ` Ralf Baechle
2001-01-16  6:10       ` 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=20010109004138.A12181@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=pmalic@blic.net \
    /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