From: Ladislav Michl <ladis@linux-mips.org>
To: Stuart Longland <stuartl@longlandclan.hopto.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Kernel 2.6 for R4600 Indy
Date: Thu, 23 Sep 2004 16:51:08 +0200 [thread overview]
Message-ID: <20040923145108.GA17740@umax645sx> (raw)
In-Reply-To: <4152D58B.608@longlandclan.hopto.org>
On Thu, Sep 23, 2004 at 11:54:19PM +1000, Stuart Longland wrote:
> Hi All,
> I've been trying to get Linux 2.6 going on my Indy for some time now.
> However, I've had little success. The machine works just fine under
> Linux 2.4.26.
>
> The kernel config is attached. Basically I've tried both booting a
> MIPS32 kernel as well as a MIPS64 kernel. In all cases, I've used the
> same kernel parameters. (root=/dev/hda3, and sometimes I put
> init=/bin/sh or single there too.)
>
> Using a MIPS32 config, the kernel boots, mounts the / filesystem, but
> then dies claiming it can't find /sbin/init.
>
> Using a MIPS64 config (built using gas-abi=o32 as suggested by Kumba),
> it doesn't even get that far:
>
> - From arcboot/SGI PROM:
> (Arcboot version 0.3.8.2)
> - -------------------------------8<--------------------------------------
> Loading program segment 2 at 0x88002000, offset=0x0, size= 0x0 328085
> Zeroing memory at 0x0032a085, size = 0x1bba3
>
> Exception: <vector=Normal>
> Status register: 0x30004803<CU1,CU0,IM7,IM4,IPL=???,MODE=KERNEL,EXL,IE>
> Cause register: 0x8010<CE=0,IP8,EXC=RADE>
> Exception PC: 0x830f018, Exception RA: 0x88804514
> Read address error exception, bad address: 0x830f018
> Local I/O interrupt register 1: 0x80 <VR/GIO2>
> Saved user regs in hex (&gpda 0xa8740e48, &_regs 0xa8741048):
> arg: a8740000 88002000 88001fe0 18
> tmp: a8740000 3 8880e0b4 830f018 8880e0b0 887fe8ec 887fe5e4 4
> sve: a8740000 3 400000 800000 16 3f80 0 10000000
> t8 a8740000 t9 ffffffff at ffffffff v0 ffffffff v1 ffffffff k1 830f018
> gp a8740000 f0 ffffffff sp ffffffff ra ffffffff
>
> PANIC: Unexpected exception
If that's more than two hours old CVS kernel then it's my fault, already fixed.
[snip]
> Apologies if this has been answered before... but I'm a bit of a newbie
> when it comes to Linux/MIPS.[2] Is there anything I missed when setting
> this all up?
We have both Indy and O2 running there, but you'll have to wait a bit
until patches appear in CVS.
Regards,
ladis
next prev parent reply other threads:[~2004-09-27 11:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 13:54 Kernel 2.6 for R4600 Indy Stuart Longland
2004-09-23 14:51 ` Ladislav Michl [this message]
2004-09-23 15:00 ` Stephen P. Becker
2004-09-24 0:16 ` Stuart Longland
2004-09-24 9:07 ` Florian Lohoff
2004-09-24 15:42 ` Stuart Longland
2004-09-24 16:44 ` Florian Lohoff
2004-09-24 13:05 ` Stephen P. Becker
2004-09-24 13:17 ` Robin Humble
2004-09-24 13:27 ` Stephen P. Becker
2004-09-24 13:43 ` Robin Humble
2004-09-24 15:13 ` Stephen P. Becker
2004-09-23 15:48 ` Florian Lohoff
2004-10-02 18:50 ` Thiemo Seufer
2004-10-02 20:40 ` Thiemo Seufer
2004-10-02 23:47 ` Thiemo Seufer
2004-10-03 0:58 ` Maciej W. Rozycki
2004-10-04 14:52 ` Ralf Baechle
2004-10-04 23:48 ` Maciej W. Rozycki
2004-10-05 19:04 ` Ralf Baechle
2004-10-05 19:35 ` Maciej W. Rozycki
2004-10-07 12:28 ` Ralf Baechle
2004-10-03 11:40 ` Thomas Bogendoerfer
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=20040923145108.GA17740@umax645sx \
--to=ladis@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=stuartl@longlandclan.hopto.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