From: Lee Revell <rlrevell@joe-job.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
david singleton <dsingleton@mvista.com>
Subject: Re: 2.6.14-rt15: cannot build with !PREEMPT_RT
Date: Mon, 28 Nov 2005 15:34:06 -0500 [thread overview]
Message-ID: <1133210046.4998.7.camel@mindpipe> (raw)
In-Reply-To: <20051128160052.GA29540@elte.hu>
On Mon, 2005-11-28 at 17:00 +0100, Ingo Molnar wrote:
> * Lee Revell <rlrevell@joe-job.com> wrote:
>
> > On Mon, 2005-11-28 at 12:48 +0100, Ingo Molnar wrote:
> > > which was the last -rt kernel that worked fine for you in
> > > PREEMPT_DESKTOP mode?
> >
> > It has been a long time, possibly months - I've mostly been using
> > PREEMPT_RT. But now I am working on a soft RT project that for
> > various reasons would like to use the mainline kernel, and I've found
> > it still has some scheduling bumps up to 5-7ms and am trying to
> > identify the problem.
>
> ok.
>
> > Would you like me to do a binary search?
>
> that would certainly be very helpful!
>
With 2.6.13-rc4-RT-V0.7.52-02 (the oldest version I still have around) I
still can't build that config, but it fails with:
LD .tmp_vmlinux1
net/built-in.o: In function `rt_check_expire':
route.c:(.text+0x1a66a): undefined reference to `__bad_spinlock_type'
route.c:(.text+0x1a68d): undefined reference to `__bad_spinlock_type'
net/built-in.o: In function `rt_run_flush':
route.c:(.text+0x1a7c1): undefined reference to `__bad_spinlock_type'
route.c:(.text+0x1a7d9): undefined reference to `__bad_spinlock_type'
net/built-in.o: In function `rt_garbage_collect':
route.c:(.text+0x1aa2a): undefined reference to `__bad_spinlock_type'
net/built-in.o:route.c:(.text+0x1aa55): more undefined references to
`__bad_spinlock_type' follow
make: *** [.tmp_vmlinux1] Error 1
AFAICT all the realtime-preempt patches have references to
__bad_spinlock_type but none of them ever define it - I can't figure out
what's going on.
I'll try to build something older.
Lee
next prev parent reply other threads:[~2005-11-28 21:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 6:52 2.6.14-rt15: cannot build with !PREEMPT_RT Lee Revell
2005-11-26 12:23 ` Ingo Molnar
2005-11-26 19:05 ` Lee Revell
2005-11-26 19:46 ` Thomas Gleixner
2005-11-27 12:30 ` Ingo Molnar
2005-11-27 19:57 ` Lee Revell
2005-11-28 11:44 ` Ingo Molnar
2005-11-28 1:27 ` Lee Revell
2005-11-28 11:48 ` Ingo Molnar
2005-11-28 14:56 ` Lee Revell
2005-11-28 16:00 ` Ingo Molnar
2005-11-28 17:50 ` Lee Revell
2005-11-28 20:34 ` Lee Revell [this message]
2005-11-28 22:40 ` Lee Revell
2005-11-29 2:08 ` Lee Revell
2005-11-29 7:29 ` Ingo Molnar
2005-11-29 9:32 ` Ingo Molnar
2005-11-29 23:19 ` Lee Revell
2005-12-09 1:05 ` Lee Revell
2005-12-10 0:25 ` Lee Revell
2005-12-12 17:44 ` 2.6.15-rc5-rt1 will not compile (was Re: 2.6.14-rt15: cannot build with !PREEMPT_RT) Lee Revell
2005-12-12 21:49 ` Steven Rostedt
2005-12-12 22:14 ` Lee Revell
2005-12-12 22:22 ` Steven Rostedt
2005-12-12 22:31 ` Lee Revell
2005-12-12 22:34 ` Steven Rostedt
2005-12-13 3:28 ` Steven Rostedt
2005-12-13 8:08 ` Ingo Molnar
2005-12-16 20:53 ` Lee Revell
2005-12-12 22:39 ` K.R. Foley
2005-12-13 8:15 ` Ingo Molnar
2005-12-13 14:32 ` [PATCH -RT] fix i386 RWSEM_GENERIC_SPINLOCK (was: Re: 2.6.15-rc5-rt1 will not compile) Steven Rostedt
2005-12-13 15:03 ` Steven Rostedt
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=1133210046.4998.7.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=dsingleton@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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