Re: 2.6.14-rt15: cannot build with !PREEMPT_RT

[Lee Revell <rlrevell@joe-job.com>]

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/