From: Ralf Baechle <ralf@oss.sgi.com>
To: Dave Gilbert <gilbertd@treblig.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: Trying to boot an Indy
Date: Sun, 21 Jan 2001 02:37:21 -0200 [thread overview]
Message-ID: <20010121023721.D853@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10101210150410.964-100000@tardis.home.dave>; from gilbertd@treblig.org on Sun, Jan 21, 2001 at 02:01:15AM +0000
On Sun, Jan 21, 2001 at 02:01:15AM +0000, Dave Gilbert wrote:
> 2) So I ftp'd the file over under Irix, gzip -d'd it and then rebooted and
> from sash did boot indyvmlinux - this immediatly after starting gave
> 'Exception: <vector=UTLB Miss>' plus details (available on request).
> (This is kernel vmlinux=001027-test9-r4x00.gz off
> download.ichilton.co.uk/pub/ichilton/linux-mips/kernels).
>
> This is an Indy R4600PC with 64MB RAM.
You may have become a victim of a sash bug which makes the firmware report
used memory as free memory and in the end results in the kernel overwriting
itself. The solution is easy; don't use sash. This means you either
have to boot the kernel via ``bootp() -f ...'' from the network or you
use IRIX's dvhtool to write it into the volume header, then boot it from
the kernel prompt by just entering the kernel name.
Ralf
next prev parent reply other threads:[~2001-01-21 4:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-21 2:01 Trying to boot an Indy Dave Gilbert
2001-01-21 4:37 ` Ralf Baechle [this message]
2001-01-21 13:27 ` Dave Gilbert
2001-01-23 16:11 ` Christoph Martin
2001-01-23 16:34 ` Dr. David Gilbert
2001-01-23 16:34 ` Dr. David Gilbert
2001-01-23 17:23 ` Wills
[not found] ` <3A84E2C4.112F8B2F@cotw.com>
2001-02-10 13:14 ` Patch for Philips Nino Steven J. Hill
2001-01-23 17:02 ` Trying to boot an Indy 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=20010121023721.D853@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=gilbertd@treblig.org \
--cc=linux-mips@oss.sgi.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