Re: 2.6.26.6-rt10

From: Luis Henriques
Date: Sun Oct 12 2008 - 20:15:37 EST


Hi Steven,

Steven Rostedt wrote:
> We are pleased to announce the 2.6.26.6-rt10 tree, which can be
> downloaded from the location:
>
> http://rt.et.redhat.com/download/
>
> Information on the RT patch can be found at:
>
> http://rt.wiki.kernel.org/index.php/Main_Page
>
> Changes since 2.6.26.5-rt9
>
> - ported to 2.6.26.6
>
> - rwlock to handle unnested order unlocks (Steven Rostedt)
>
> - rwlock update torture test to test unnested unlocks (Steven Rostedt)
>
> - remove rt push comment (Gregory Haskins)
>
> - rt sched fix to handle dequeue (Gregory Haskins)
>
> - PPC: remove duplicate stack trace code (Robert Schwebel)
>
> - ARM: ftrace event IRQ call fix (Alexander Pazdnikov)
>
> - fair sched not to resched RT tasks (Peter Zijlstra)
>
> - ftrace quick stop (Steven Rostedt)
>
> - event trace of resched (Steven Rostedt)
>
>
> to build a 2.6.26.6-rt10 tree, the following patches should be applied:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.tar.bz2
> http://kernel.org/pub/linux/kernel/v2.6/patch-2.6.26.6.bz2
> http://rt.et.redhat.com/download/patch-2.6.26.6-rt10.bz2
>
>
>
> And like always, my RT version of Matt Mackall's ketchup will get this
> for you nicely:
>
> http://people.redhat.com/srostedt/rt/tools/ketchup-0.9.8-rt3
>
>
> The broken out patches are also available.
>
>
> -- Steve
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>

I found a compilation error while compiling this new version of the rt
pach. I guess the following line is enough for you to trace the problem:

kernel/trace/trace_events.c:49: error: ‘function_trace_stop’ undeclared
(first use in this function)

It seems that an 'extern int function_trace_stop' is missing somewhere...

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