From: Kars de Jong <jongk@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen N Chivers <schivers@csc.com.au>,
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: Thu, 13 Nov 2008 23:01:16 +0100 [thread overview]
Message-ID: <1226613676.4267.20.camel@kars.perseus.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0811132244320.11953@anakin>
On do, 2008-11-13 at 22:48 +0100, Geert Uytterhoeven wrote:
> On Thu, 13 Nov 2008, Kars de Jong wrote:
> > On di, 2008-11-11 at 11:01 +0100, Geert Uytterhoeven wrote:
> > > 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.
> > > >
> > > > 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").
> >
> > Hm, no fair! I already reported this bug back in 2006, asking for
> > feedback:
> >
> > http://www.nabble.com/Re%3A-CVS-Update%3A-linux-tt6999670.html
> >
> > ... but I never got any ;)
>
> Bummer...
>
> > By the way, I tested Linus' HEAD today (with your quilt patches, Geert)
> > on my MVME167, it only needed the above fixed and it booted.
>
> OK. Can I add your Tested-by? Then I'll forward it to Linus ASAP.
Yes, no problem, if your patch would look something like this (I like
git already!):
diff --git a/arch/m68k/kernel/ints.c b/arch/m68k/kernel/ints.c
index 7e8a0d3..761ee04 100644
--- a/arch/m68k/kernel/ints.c
+++ b/arch/m68k/kernel/ints.c
@@ -133,7 +133,7 @@ void __init m68k_setup_user_interrupt(unsigned int vec, unsigned int cnt,
{
int i;
- BUG_ON(IRQ_USER + cnt >= NR_IRQS);
+ BUG_ON(IRQ_USER + cnt > NR_IRQS);
m68k_first_user_vec = vec;
for (i = 0; i < cnt; i++)
irq_controller[IRQ_USER + i] = &user_irq_controller;
next prev parent reply other threads:[~2008-11-13 22:23 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 ` Kernel 2.6.24, binutils-2.18, and tftplilo on diskless MVME167 Geert Uytterhoeven
2008-11-13 21:33 ` Kars de Jong
2008-11-13 21:48 ` Geert Uytterhoeven
2008-11-13 22:01 ` Kars de Jong [this message]
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=1226613676.4267.20.camel@kars.perseus.home \
--to=jongk@linux-m68k.org \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.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