From: Jay Maynard <jmaynard@conmicro.cx>
To: linux-alpha@vger.kernel.org
Subject: Re: 2.4 kernels broken on Takara?
Date: Sun, 8 Feb 2004 17:53:12 -0600 [thread overview]
Message-ID: <20040208175312.A26586@thebrain.conmicro.cx> (raw)
In-Reply-To: <20040208211454.GV28571@lug-owl.de>; from jbglaw@lug-owl.de on Sun, Feb 08, 2004 at 10:14:55PM +0100
On Sun, Feb 08, 2004 at 10:14:55PM +0100, Jan-Benedict Glaw wrote:
> On Sun, 2004-02-08 10:39:09 -0600, Jay Maynard <jmaynard@conmicro.cx>
> wrote in message <20040208103909.C25099@thebrain.conmicro.cx>:
> > install. I've tried installing a Debian system, then a 2.4 kernel on top of
> > that - but 2.4.18 and 2.4.24 prebuilt generic kernels, as well as a 2.4.24
> > custom kernel built specifically for the Takara, all blow up with a kernel
> > paging error during startup, right after the PCI bridges are detected. The
> > 2.2.20 kernel iinstalled by Debian runs fine.
> I remember there were problems with the PCI bridging code. Maybe you'd
> try to give 2.6.x a shot...
No luck, although I got a little better look at the error messages. I've
retyped them here:
PCI: Bus 2, bridge: 0000:00:14.0
IO window: 8000-8fff
MEM window: 02400000-037fffff
PREFETCH window: 02200000-022fffff
PCI: Setting latency timer of device 0000:00:13.0 to 64
Unable to handle kernel paging request at virtual address 0000000000000040
swapper(1): Oops 0
pc = [<fffffc00004eecf0>] ra = [<fffffc00004eecc8>] ps = 0000 Not tainted
[register dump here]
Trace:fffffc0000310124 fffffc00003151e8
Code: 261dfff1 401f0000 a4410038 2c810078 20210078 22107a7c <a0420040>
488100c4
Kernel panic: Attempted to kill init!
This is with the generic Debian 2.6.0 kernel. Now what?
next prev parent reply other threads:[~2004-02-08 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 16:39 2.4 kernels broken on Takara? Jay Maynard
2004-02-08 21:14 ` Jan-Benedict Glaw
2004-02-08 23:53 ` Jay Maynard [this message]
2004-02-09 9:02 ` Jan-Benedict Glaw
2004-02-09 13:57 ` Jay Maynard
2004-02-10 0:42 ` Jay Maynard
2004-02-09 11:56 ` Thomas Steudten
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=20040208175312.A26586@thebrain.conmicro.cx \
--to=jmaynard@conmicro.cx \
--cc=linux-alpha@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.