From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen N Chivers <schivers@csc.com.au>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Andreas Schwab <schwab@suse.de>,
Debian GNU/Linux m68k <debian-68k@lists.debian.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Kernel 2.6.24, binutils-2.18, and tftplilo on diskless MVME167.
Date: Tue, 11 Nov 2008 11:01:20 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0811111055100.19341@anakin> (raw)
In-Reply-To: <OFF2D16A54.2029BAD8-ONCA2574FD.0079BF46-CA2574FE.000FBF52@csc.com>
On Tue, 11 Nov 2008, Stephen N Chivers wrote:
> In the past few days I have attempted to get 2.6 kernels booting on my
> diskless MVME167 boards.
> I have tried several kernels, including:
> linux-image-2.6.26-1-mvme16x_2.6.26-9_m68k.deb.
>
> None of them appear to continue beyond the initialisation code in:
>
> arch/m68k/kernel/head.S
>
> They load normally via tftplilo and commence executing, apparently stopping
> with the only
> diagnostic available at the console being the magic:
>
> ABCGHIJK
>
> In frustration, I compiled my own 2.6.24 kernel from clean source using a
> cross compilation
> system based on binutils-2.18 and gcc-4.1.2. The linking of vmlinux failed
> with the infamous:
>
> m68k-linux-gnu-ld: .tmp_vmlinux1: Not enough room for program
> headers, try linking with -N
>
> I applied the patch for vmlinux-std.lds provided by Andreas Schwab:
>
> http://marc.info/?l=linux-m68k&m=120596505621019&w=2
That patch is not in the m68k tree. It also doesn't apply anymore, as we
already have a NOTES somewhere else now.
Do you still need it on e.g. 2.6.27?
> I traced the "freeze" of the kernel to the 'BUG_ON' test in
> 'm68k_setup_user_interrupt' in file
> arch/m68k/ints.c:
>
> BUG_ON(IRQ_USER + cnt >= NR_IRQS);
>
> Now, for the VME boards, IRQ_USER is 8, cnt is 192 and NR_IRQS is 200. So
> this test will
> trigger the BUG_ON action, and so the kernel appears to stop without
> logging any diagnostics.
Oops, that looks like an off-by-one error. It has been introduced by commit
69961c375288bdab7604e0bb1c8d22999bb8a347 ("[PATCH] m68k/Atari: Interrupt
updates").
I'll fix it.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next parent reply other threads:[~2008-11-11 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFF2D16A54.2029BAD8-ONCA2574FD.0079BF46-CA2574FE.000FBF52@csc.com>
2008-11-11 10:01 ` Geert Uytterhoeven [this message]
2008-11-13 21:33 ` Kernel 2.6.24, binutils-2.18, and tftplilo on diskless MVME167 Kars de Jong
2008-11-13 21:48 ` Geert Uytterhoeven
2008-11-13 22:01 ` Kars de Jong
2008-11-14 7:11 ` Geert Uytterhoeven
2008-11-13 23:01 ` Finn Thain
[not found] ` <1226656883.21315.4.camel@kars.perseus.home>
2008-11-14 11:14 ` Finn Thain
2008-11-14 14:37 ` Finn Thain
2008-11-14 0:04 ` Stephen N Chivers
2008-11-13 23:59 ` Stephen N Chivers
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=Pine.LNX.4.64.0811111055100.19341@anakin \
--to=geert@linux-m68k.org \
--cc=debian-68k@lists.debian.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schivers@csc.com.au \
--cc=schwab@suse.de \
--cc=zippel@linux-m68k.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