Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Sun, 2005-04-10 at 19:47 +0200, Ingo Molnar wrote: > yeah, that's what i did in -45-01. > Ingo, This build failure was reported with 45-01 by an AMD64 user. Do you need the .config? HOSTCC scripts/bin2c CC arch/x86_64/kernel/asm-offsets.s CHK include/asm-x86_64/offset.h UPD include/asm-x86_64/offset.h CC init/main.o In file included from include/linux/rwsem.h:38, from include/linux/kobject.h:24, from include/linux/module.h:19, from init/main.c:16: include/asm/rwsem.h:55: error: redefinition of `struct rw_semaphore' In file included from include/linux/rwsem.h:38, from include/linux/kobject.h:24, from include/linux/module.h:19, from init/main.c:16: include/asm/rwsem.h:79:1: warning: "__RWSEM_INITIALIZER" redefined In file included from include/linux/spinlock.h:16, from include/linux/capability.h:45, from include/linux/sched.h:7, from include/linux/module.h:10, from init/main.c:16: include/linux/rt_lock.h:295:1: warning: this is the location of the previous definition In file included from include/linux/rwsem.h:38, from include/linux/kobject.h:24, from include/linux/module.h:19, from init/main.c:16: include/asm/rwsem.h:83:1: warning: "DECLARE_RWSEM" redefined In file included from include/linux/spinlock.h:16, from include/linux/capability.h:45, from include/linux/sched.h:7, from include/linux/module.h:10, from init/main.c:16: include/linux/rt_lock.h:298:1: warning: this is the location of the previous definition include/asm/rwsem.h:86: error: parse error before "do" In file included from include/linux/kobject.h:24, from include/linux/module.h:19, from init/main.c:16: include/linux/rwsem.h: In function `compat_down_read': include/linux/rwsem.h:56: warning: passing arg 1 of `__down_read' from incompatible pointer type include/linux/rwsem.h: In function `compat_down_read_trylock': include/linux/rwsem.h:67: warning: passing arg 1 of `__down_read_trylock' from incompatible pointer type include/linux/rwsem.h: In function `compat_down_write': include/linux/rwsem.h:79: warning: passing arg 1 of `__down_write' from incompatible pointer type include/linux/rwsem.h: In function `compat_down_write_trylock': include/linux/rwsem.h:90: warning: passing arg 1 of `__down_write_trylock' from incompatible pointer type include/linux/rwsem.h: In function `compat_up_read': include/linux/rwsem.h:101: warning: passing arg 1 of `__up_read' from incompatible pointer type include/linux/rwsem.h: In function `compat_up_write': include/linux/rwsem.h:111: warning: passing arg 1 of `__up_write' from incompatible pointer type include/linux/rwsem.h: In function `compat_downgrade_write': include/linux/rwsem.h:121: warning: passing arg 1 of `__downgrade_write' from incompatible pointer type In file included from include/linux/proc_fs.h:6, from init/main.c:17: include/linux/fs.h: In function `lock_super': include/linux/fs.h:828: warning: implicit declaration of function `compat_down' include/linux/fs.h: In function `unlock_super': include/linux/fs.h:833: warning: implicit declaration of function `compat_up' make[1]: *** [init/main.o] Error 1 make: *** [init] Error 2 Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Sun, 2005-04-10 at 19:47 +0200, Ingo Molnar wrote: yeah, that's what i did in -45-01. Ingo, This build failure was reported with 45-01 by an AMD64 user. Do you need the .config? HOSTCC scripts/bin2c CC arch/x86_64/kernel/asm-offsets.s CHK include/asm-x86_64/offset.h UPD include/asm-x86_64/offset.h CC init/main.o In file included from include/linux/rwsem.h:38, from include/linux/kobject.h:24, from include/linux/module.h:19, from init/main.c:16: include/asm/rwsem.h:55: error: redefinition of `struct rw_semaphore' In file included from include/linux/rwsem.h:38, from include/linux/kobject.h:24, from include/linux/module.h:19, from init/main.c:16: include/asm/rwsem.h:79:1: warning: __RWSEM_INITIALIZER redefined In file included from include/linux/spinlock.h:16, from include/linux/capability.h:45, from include/linux/sched.h:7, from include/linux/module.h:10, from init/main.c:16: include/linux/rt_lock.h:295:1: warning: this is the location of the previous definition In file included from include/linux/rwsem.h:38, from include/linux/kobject.h:24, from include/linux/module.h:19, from init/main.c:16: include/asm/rwsem.h:83:1: warning: DECLARE_RWSEM redefined In file included from include/linux/spinlock.h:16, from include/linux/capability.h:45, from include/linux/sched.h:7, from include/linux/module.h:10, from init/main.c:16: include/linux/rt_lock.h:298:1: warning: this is the location of the previous definition include/asm/rwsem.h:86: error: parse error before do In file included from include/linux/kobject.h:24, from include/linux/module.h:19, from init/main.c:16: include/linux/rwsem.h: In function `compat_down_read': include/linux/rwsem.h:56: warning: passing arg 1 of `__down_read' from incompatible pointer type include/linux/rwsem.h: In function `compat_down_read_trylock': include/linux/rwsem.h:67: warning: passing arg 1 of `__down_read_trylock' from incompatible pointer type include/linux/rwsem.h: In function `compat_down_write': include/linux/rwsem.h:79: warning: passing arg 1 of `__down_write' from incompatible pointer type include/linux/rwsem.h: In function `compat_down_write_trylock': include/linux/rwsem.h:90: warning: passing arg 1 of `__down_write_trylock' from incompatible pointer type include/linux/rwsem.h: In function `compat_up_read': include/linux/rwsem.h:101: warning: passing arg 1 of `__up_read' from incompatible pointer type include/linux/rwsem.h: In function `compat_up_write': include/linux/rwsem.h:111: warning: passing arg 1 of `__up_write' from incompatible pointer type include/linux/rwsem.h: In function `compat_downgrade_write': include/linux/rwsem.h:121: warning: passing arg 1 of `__downgrade_write' from incompatible pointer type In file included from include/linux/proc_fs.h:6, from init/main.c:17: include/linux/fs.h: In function `lock_super': include/linux/fs.h:828: warning: implicit declaration of function `compat_down' include/linux/fs.h: In function `unlock_super': include/linux/fs.h:833: warning: implicit declaration of function `compat_up' make[1]: *** [init/main.o] Error 1 make: *** [init] Error 2 Lee - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
* Steven Rostedt <[EMAIL PROTECTED]> wrote:
> Would there be any harm with changing that to
>
> #define jbd_debug(f, a...) do {} while(0)
>
> The compiler would strip it anyway, and you wouldn't have to worry
> about your scripts removing the macro.
yeah, that's what i did in -45-01. Since it's not the first time this
has happened i might have to change the marker to /*I*/ or something
like that :-)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Sun, 2005-04-10 at 19:27 +0200, Ingo Molnar wrote:
> * K.R. Foley <[EMAIL PROTECTED]> wrote:
>
> > Ingo,
> >
> > It would seem that in the latest patch RT-V0.7.45-00 we have reverted
> > back to removing the define of jbd_debug which the attached patch
> > (against one of the 2.6.11 versions) fixed.
>
> > +#define jbd_debug(f, a...) /**/
>
> oops, indeed. '/**/' happens to be my private marker for 'debug code',
> which the release scripts automatically strip from the files ...
>
> i've uploaded -45-01 with the fix.
>
Would there be any harm with changing that to
#define jbd_debug(f, a...) do {} while(0)
The compiler would strip it anyway, and you wouldn't have to worry about
your scripts removing the macro.
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
* K.R. Foley <[EMAIL PROTECTED]> wrote: > Ingo, > > It would seem that in the latest patch RT-V0.7.45-00 we have reverted > back to removing the define of jbd_debug which the attached patch > (against one of the 2.6.11 versions) fixed. > +#define jbd_debug(f, a...) /**/ oops, indeed. '/**/' happens to be my private marker for 'debug code', which the release scripts automatically strip from the files ... i've uploaded -45-01 with the fix. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
Ingo, It would seem that in the latest patch RT-V0.7.45-00 we have reverted back to removing the define of jbd_debug which the attached patch (against one of the 2.6.11 versions) fixed. -- kr --- linux-2.6.11/include/linux/jbd.h.orig 2005-03-16 09:18:51.0 -0600 +++ linux-2.6.11/include/linux/jbd.h2005-03-16 09:19:24.0 -0600 @@ -65,6 +65,7 @@ extern int journal_enable_debug; } \ } while (0) #else +#define jbd_debug(f, a...) /**/ #endif extern void * __jbd_kmalloc (const char *where, size_t size, int flags, int retry);
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
Ingo, It would seem that in the latest patch RT-V0.7.45-00 we have reverted back to removing the define of jbd_debug which the attached patch (against one of the 2.6.11 versions) fixed. -- kr --- linux-2.6.11/include/linux/jbd.h.orig 2005-03-16 09:18:51.0 -0600 +++ linux-2.6.11/include/linux/jbd.h2005-03-16 09:19:24.0 -0600 @@ -65,6 +65,7 @@ extern int journal_enable_debug; } \ } while (0) #else +#define jbd_debug(f, a...) /**/ #endif extern void * __jbd_kmalloc (const char *where, size_t size, int flags, int retry);
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
* K.R. Foley [EMAIL PROTECTED] wrote: Ingo, It would seem that in the latest patch RT-V0.7.45-00 we have reverted back to removing the define of jbd_debug which the attached patch (against one of the 2.6.11 versions) fixed. +#define jbd_debug(f, a...) /**/ oops, indeed. '/**/' happens to be my private marker for 'debug code', which the release scripts automatically strip from the files ... i've uploaded -45-01 with the fix. Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Sun, 2005-04-10 at 19:27 +0200, Ingo Molnar wrote:
* K.R. Foley [EMAIL PROTECTED] wrote:
Ingo,
It would seem that in the latest patch RT-V0.7.45-00 we have reverted
back to removing the define of jbd_debug which the attached patch
(against one of the 2.6.11 versions) fixed.
+#define jbd_debug(f, a...) /**/
oops, indeed. '/**/' happens to be my private marker for 'debug code',
which the release scripts automatically strip from the files ...
i've uploaded -45-01 with the fix.
Would there be any harm with changing that to
#define jbd_debug(f, a...) do {} while(0)
The compiler would strip it anyway, and you wouldn't have to worry about
your scripts removing the macro.
-- Steve
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
* Steven Rostedt [EMAIL PROTECTED] wrote:
Would there be any harm with changing that to
#define jbd_debug(f, a...) do {} while(0)
The compiler would strip it anyway, and you wouldn't have to worry
about your scripts removing the macro.
yeah, that's what i did in -45-01. Since it's not the first time this
has happened i might have to change the marker to /*I*/ or something
like that :-)
Ingo
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
Lee Revell wrote: On Fri, 2005-04-08 at 15:26 -0500, K.R. Foley wrote: Lee Revell wrote: Meh, I'll try again, maybe it's some weird NFS problem. Lee Hmm. Maybe. I should probably mention that I am doing an FC3 install via NFS from my older SMP system right now while also building V0.7.44-03. Tried again and it works. Weird... Lee Very wierd. It worries me when things like that happen. ;-) -- kr - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Fri, 2005-04-08 at 15:26 -0500, K.R. Foley wrote: > Lee Revell wrote: > > > > Meh, I'll try again, maybe it's some weird NFS problem. > > > > Lee > > > > Hmm. Maybe. I should probably mention that I am doing an FC3 install via > NFS from my older SMP system right now while also building V0.7.44-03. > Tried again and it works. Weird... Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
Lee Revell wrote: On Fri, 2005-04-08 at 15:15 -0500, K.R. Foley wrote: Lee Revell wrote: On Fri, 2005-04-08 at 16:22 +0100, Rui Nuno Capela wrote: Our first victim!! :-) No kidding!? V0.7.44-02 does not even compile for me. It appears to be full of merge errors. I must be in the twilight zone over here. V0.7.44-02 runs fine on my UP system, my older SMP system (although I have to compile in my SCSI drivers, but that has nothing to do with this patch) and my faster P4/HT SMP system at the office. Meh, I'll try again, maybe it's some weird NFS problem. Lee Hmm. Maybe. I should probably mention that I am doing an FC3 install via NFS from my older SMP system right now while also building V0.7.44-03. -- kr - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Fri, 2005-04-08 at 15:15 -0500, K.R. Foley wrote: > Lee Revell wrote: > > On Fri, 2005-04-08 at 16:22 +0100, Rui Nuno Capela wrote: > > > >>>Our first victim!! :-) > >>> > >> > >>No kidding!? > >> > > > > > > V0.7.44-02 does not even compile for me. It appears to be full of merge > > errors. > > > > I must be in the twilight zone over here. V0.7.44-02 runs fine on my UP > system, my older SMP system (although I have to compile in my SCSI > drivers, but that has nothing to do with this patch) and my faster P4/HT > SMP system at the office. Meh, I'll try again, maybe it's some weird NFS problem. Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Fri, 2005-04-08 at 16:22 +0100, Rui Nuno Capela wrote: > > Our first victim!! :-) > > > > No kidding!? > V0.7.44-02 does not even compile for me. It appears to be full of merge errors. I get these errors with "make oldconfig": HOSTLD scripts/kconfig/conf scripts/kconfig/conf -o arch/i386/Kconfig lib/Kconfig.RT:160:warning: choice values currently only support a single prompt lib/Kconfig.RT:173:warning: choice values currently only support a single prompt lib/Kconfig.RT:190:warning: choice values currently only support a single prompt lib/Kconfig.RT:211:warning: choice values currently only support a single prompt lib/Kconfig.RT:7:warning: choice values currently only support a single prompt lib/Kconfig.RT:20:warning: choice values currently only support a single prompt lib/Kconfig.RT:37:warning: choice values currently only support a single prompt lib/Kconfig.RT:58:warning: choice values currently only support a single prompt # # using defaults found in .config Then, looks like mcount-wrapper.S is two copies of the same file. To have any chance of building this patch was required: --- arch/i386/kernel/mcount-wrapper.S~ 2005-04-07 19:02:33.0 -0400 +++ arch/i386/kernel/mcount-wrapper.S 2005-04-07 19:52:24.0 -0400 @@ -25,30 +25,3 @@ out: ret -/* - * linux/arch/i386/mcount-wrapper.S - * - * Copyright (C) 2004 Ingo Molnar - */ - -.globl mcount -mcount: - - cmpl $0, mcount_enabled - jz out - - push %ebp - mov %esp, %ebp - pushl %eax - pushl %ecx - pushl %edx - - call __mcount - - popl %edx - popl %ecx - popl %eax - popl %ebp -out: - ret - And it still bombs out here. This is where I gave up: CC kernel/rt.o kernel/rt.c:1931: error: redefinition of `pi_lock' kernel/rt.c:55: error: `pi_lock' previously defined here kernel/rt.c:2037: error: redefinition of `zap_rt_locks' kernel/rt.c:161: error: `zap_rt_locks' previously defined here kernel/rt.c:2382: error: redefinition of `check_pi_list_present' kernel/rt.c:555: error: `check_pi_list_present' previously defined here kernel/rt.c:2387: error: redefinition of `check_pi_list_empty' kernel/rt.c:560: error: `check_pi_list_empty' previously defined here kernel/rt.c:2398: error: redefinition of `change_owner' kernel/rt.c:571: error: `change_owner' previously defined here kernel/rt.c:2420: error: redefinition of `pi_setprio' kernel/rt.c:593: error: `pi_setprio' previously defined here [etc] Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
> Our first victim!! :-) > No kidding!? > On Tue, 2005-04-05 at 20:06 +0100, Rui Nuno Capela wrote: >> > >> I'm having plenty of this on boot, on my SMP/HT desktop (P4/x86), while >> running RT-V0.7.44-01 (SMP+PREEMPT_RT): >> >> BUG: kstopmachine: RT task yield()-ing! >> >> See sample dmesg and .config on attach. >> >> OTOH, on my laptop (P4/UP), all seems to be clear fine. >> > > The kstopmachine is only run on SMP environments, so it won't show up on > your UP machine. > > >> Is this something to be affraid of? :) >> > > If your box is still running, then no. But it's now a chore to remove > the yield from this algorithm, since yields have a possibility to > deadlock the system. Although in this particular case, it may not be a > problem, since the threads that are being waited on are created for > other CPUs. But I haven't looked too much into what stop_machine is > doing so I can very well be wrong. > > Thank you for reporting it, we want to weed out all the yields that a RT > task may call. > Now, I'm sure my fears were reasonable. With RT-V0.7.44-02 SMP a can't even reach an usable system state. This weird BUG: kstopmachine: RT task yield()-ing! is flooding the init process to death. Completely. Hard-reset is the only viable solution to a fast scrolling console dump, which seems to be in a terrible, nasty and endless loop. I'm not afraid anymore. RT-0.7.44-02 is useless on my P4 SMP/HT desktop machine. ;) Bye. -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] config-2.6.12-rc2-RT-V0.7.44-02.0smp.gz Description: GNU Zip compressed data
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
Our first victim!! :-) No kidding!? On Tue, 2005-04-05 at 20:06 +0100, Rui Nuno Capela wrote: I'm having plenty of this on boot, on my SMP/HT desktop (P4/x86), while running RT-V0.7.44-01 (SMP+PREEMPT_RT): BUG: kstopmachine: RT task yield()-ing! See sample dmesg and .config on attach. OTOH, on my laptop (P4/UP), all seems to be clear fine. The kstopmachine is only run on SMP environments, so it won't show up on your UP machine. Is this something to be affraid of? :) If your box is still running, then no. But it's now a chore to remove the yield from this algorithm, since yields have a possibility to deadlock the system. Although in this particular case, it may not be a problem, since the threads that are being waited on are created for other CPUs. But I haven't looked too much into what stop_machine is doing so I can very well be wrong. Thank you for reporting it, we want to weed out all the yields that a RT task may call. Now, I'm sure my fears were reasonable. With RT-V0.7.44-02 SMP a can't even reach an usable system state. This weird BUG: kstopmachine: RT task yield()-ing! is flooding the init process to death. Completely. Hard-reset is the only viable solution to a fast scrolling console dump, which seems to be in a terrible, nasty and endless loop. I'm not afraid anymore. RT-0.7.44-02 is useless on my P4 SMP/HT desktop machine. ;) Bye. -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] config-2.6.12-rc2-RT-V0.7.44-02.0smp.gz Description: GNU Zip compressed data
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Fri, 2005-04-08 at 16:22 +0100, Rui Nuno Capela wrote: Our first victim!! :-) No kidding!? V0.7.44-02 does not even compile for me. It appears to be full of merge errors. I get these errors with make oldconfig: HOSTLD scripts/kconfig/conf scripts/kconfig/conf -o arch/i386/Kconfig lib/Kconfig.RT:160:warning: choice values currently only support a single prompt lib/Kconfig.RT:173:warning: choice values currently only support a single prompt lib/Kconfig.RT:190:warning: choice values currently only support a single prompt lib/Kconfig.RT:211:warning: choice values currently only support a single prompt lib/Kconfig.RT:7:warning: choice values currently only support a single prompt lib/Kconfig.RT:20:warning: choice values currently only support a single prompt lib/Kconfig.RT:37:warning: choice values currently only support a single prompt lib/Kconfig.RT:58:warning: choice values currently only support a single prompt # # using defaults found in .config Then, looks like mcount-wrapper.S is two copies of the same file. To have any chance of building this patch was required: --- arch/i386/kernel/mcount-wrapper.S~ 2005-04-07 19:02:33.0 -0400 +++ arch/i386/kernel/mcount-wrapper.S 2005-04-07 19:52:24.0 -0400 @@ -25,30 +25,3 @@ out: ret -/* - * linux/arch/i386/mcount-wrapper.S - * - * Copyright (C) 2004 Ingo Molnar - */ - -.globl mcount -mcount: - - cmpl $0, mcount_enabled - jz out - - push %ebp - mov %esp, %ebp - pushl %eax - pushl %ecx - pushl %edx - - call __mcount - - popl %edx - popl %ecx - popl %eax - popl %ebp -out: - ret - And it still bombs out here. This is where I gave up: CC kernel/rt.o kernel/rt.c:1931: error: redefinition of `pi_lock' kernel/rt.c:55: error: `pi_lock' previously defined here kernel/rt.c:2037: error: redefinition of `zap_rt_locks' kernel/rt.c:161: error: `zap_rt_locks' previously defined here kernel/rt.c:2382: error: redefinition of `check_pi_list_present' kernel/rt.c:555: error: `check_pi_list_present' previously defined here kernel/rt.c:2387: error: redefinition of `check_pi_list_empty' kernel/rt.c:560: error: `check_pi_list_empty' previously defined here kernel/rt.c:2398: error: redefinition of `change_owner' kernel/rt.c:571: error: `change_owner' previously defined here kernel/rt.c:2420: error: redefinition of `pi_setprio' kernel/rt.c:593: error: `pi_setprio' previously defined here [etc] Lee - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Fri, 2005-04-08 at 15:15 -0500, K.R. Foley wrote: Lee Revell wrote: On Fri, 2005-04-08 at 16:22 +0100, Rui Nuno Capela wrote: Our first victim!! :-) No kidding!? V0.7.44-02 does not even compile for me. It appears to be full of merge errors. I must be in the twilight zone over here. V0.7.44-02 runs fine on my UP system, my older SMP system (although I have to compile in my SCSI drivers, but that has nothing to do with this patch) and my faster P4/HT SMP system at the office. Meh, I'll try again, maybe it's some weird NFS problem. Lee - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
Lee Revell wrote: On Fri, 2005-04-08 at 15:15 -0500, K.R. Foley wrote: Lee Revell wrote: On Fri, 2005-04-08 at 16:22 +0100, Rui Nuno Capela wrote: Our first victim!! :-) No kidding!? V0.7.44-02 does not even compile for me. It appears to be full of merge errors. I must be in the twilight zone over here. V0.7.44-02 runs fine on my UP system, my older SMP system (although I have to compile in my SCSI drivers, but that has nothing to do with this patch) and my faster P4/HT SMP system at the office. Meh, I'll try again, maybe it's some weird NFS problem. Lee Hmm. Maybe. I should probably mention that I am doing an FC3 install via NFS from my older SMP system right now while also building V0.7.44-03. -- kr - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
On Fri, 2005-04-08 at 15:26 -0500, K.R. Foley wrote: Lee Revell wrote: Meh, I'll try again, maybe it's some weird NFS problem. Lee Hmm. Maybe. I should probably mention that I am doing an FC3 install via NFS from my older SMP system right now while also building V0.7.44-03. Tried again and it works. Weird... Lee - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
Lee Revell wrote: On Fri, 2005-04-08 at 15:26 -0500, K.R. Foley wrote: Lee Revell wrote: Meh, I'll try again, maybe it's some weird NFS problem. Lee Hmm. Maybe. I should probably mention that I am doing an FC3 install via NFS from my older SMP system right now while also building V0.7.44-03. Tried again and it works. Weird... Lee Very wierd. It worries me when things like that happen. ;-) -- kr - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
Our first victim!! :-) On Tue, 2005-04-05 at 20:06 +0100, Rui Nuno Capela wrote: > > > I'm having plenty of this on boot, on my SMP/HT desktop (P4/x86), while > running RT-V0.7.44-01 (SMP+PREEMPT_RT): > > BUG: kstopmachine: RT task yield()-ing! > > See sample dmesg and .config on attach. > > OTOH, on my laptop (P4/UP), all seems to be clear fine. > The kstopmachine is only run on SMP environments, so it won't show up on your UP machine. > Is this something to be affraid of? :) > If your box is still running, then no. But it's now a chore to remove the yield from this algorithm, since yields have a possibility to deadlock the system. Although in this particular case, it may not be a problem, since the threads that are being waited on are created for other CPUs. But I haven't looked too much into what stop_machine is doing so I can very well be wrong. Thank you for reporting it, we want to weed out all the yields that a RT task may call. -- Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
> > i have released the -V0.7.44-00 Real-Time Preemption patch, which can be > downloaded from the usual place: > >http://redhat.com/~mingo/realtime-preempt/ > I'm having plenty of this on boot, on my SMP/HT desktop (P4/x86), while running RT-V0.7.44-01 (SMP+PREEMPT_RT): BUG: kstopmachine: RT task yield()-ing! See sample dmesg and .config on attach. OTOH, on my laptop (P4/UP), all seems to be clear fine. Is this something to be affraid of? :) Cheers. -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED]Linux version 2.6.12-rc2-RT-V0.7.44-01.0smp ([EMAIL PROTECTED]) (gcc version 3.3.4 (pre 3.3.5 20040809)) #1 SMP Tue Apr 5 19:21:11 WEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e8000 - 0010 (reserved) BIOS-e820: 0010 - 3ff3 (usable) BIOS-e820: 3ff3 - 3ff4 (ACPI data) BIOS-e820: 3ff4 - 3fff (ACPI NVS) BIOS-e820: 3fff - 4000 (reserved) BIOS-e820: ffb8 - 0001 (reserved) 127MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000ff780 On node 0 totalpages: 261936 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:16 HighMem zone: 32560 pages, LIFO batch:7 DMI 2.3 present. ACPI: RSDP (v002 ACPIAM) @ 0x000f9e60 ACPI: XSDT (v001 A M I OEMXSDT 0x08000320 MSFT 0x0097) @ 0x3ff30100 ACPI: FADT (v003 A M I OEMFACP 0x08000320 MSFT 0x0097) @ 0x3ff30290 ACPI: MADT (v001 A M I OEMAPIC 0x08000320 MSFT 0x0097) @ 0x3ff30390 ACPI: OEMB (v001 A M I OEMBIOS 0x08000320 MSFT 0x0097) @ 0x3ff40040 ACPI: DSDT (v001 P4P81 P4P81086 0x0086 INTL 0x02002026) @ 0x ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:2 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:2 APIC version 20 ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 4000 (gap: 4000:bfb8) Real-Time Preemption Support (c) Ingo Molnar Built 1 zonelists Kernel command line: root=/dev/hda2 mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 3360.970 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1035212k/1047744k available (1872k kernel code, 12144k reserved, 598k data, 176k init, 130240k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 6668.28 BogoMIPS (lpj=3334144) Security Framework v1.0.0 initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 4400 CPU: After vendor identify, caps: bfebfbff 4400 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 CPU: After all inits, caps: bfebfbff 0080 4400 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. CPU0: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 Booting processor 1/1 eip 2000 Initializing CPU#1 Calibrating delay loop... 6717.44 BogoMIPS (lpj=3358720) CPU: After generic identify, caps: bfebfbff 4400 CPU: After vendor identify, caps: bfebfbff 4400 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 CPU: After all inits, caps: bfebfbff 0080 4400 CPU1: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 Total of 2 processors activated (13385.72 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 checking TSC synchronization across 2 CPUs: passed. spawn_desched_task() desched cpu_callback 3/ ksoftirqd started up. softirq RT prio: 24. desched cpu_callback 2/ desched thread 0 started up. desched cpu_callback 3/0001 desched cpu_callback 2/0001 ksoftirqd started up. softirq RT prio: 24. Brought up 2 CPUs desched thread 1 started up. CPU0 attaching sched-domain: domain 0: span 3 groups: 1 2 domain 1:
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
i have released the -V0.7.44-00 Real-Time Preemption patch, which can be downloaded from the usual place: http://redhat.com/~mingo/realtime-preempt/ I'm having plenty of this on boot, on my SMP/HT desktop (P4/x86), while running RT-V0.7.44-01 (SMP+PREEMPT_RT): BUG: kstopmachine: RT task yield()-ing! See sample dmesg and .config on attach. OTOH, on my laptop (P4/UP), all seems to be clear fine. Is this something to be affraid of? :) Cheers. -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED]Linux version 2.6.12-rc2-RT-V0.7.44-01.0smp ([EMAIL PROTECTED]) (gcc version 3.3.4 (pre 3.3.5 20040809)) #1 SMP Tue Apr 5 19:21:11 WEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e8000 - 0010 (reserved) BIOS-e820: 0010 - 3ff3 (usable) BIOS-e820: 3ff3 - 3ff4 (ACPI data) BIOS-e820: 3ff4 - 3fff (ACPI NVS) BIOS-e820: 3fff - 4000 (reserved) BIOS-e820: ffb8 - 0001 (reserved) 127MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000ff780 On node 0 totalpages: 261936 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:16 HighMem zone: 32560 pages, LIFO batch:7 DMI 2.3 present. ACPI: RSDP (v002 ACPIAM) @ 0x000f9e60 ACPI: XSDT (v001 A M I OEMXSDT 0x08000320 MSFT 0x0097) @ 0x3ff30100 ACPI: FADT (v003 A M I OEMFACP 0x08000320 MSFT 0x0097) @ 0x3ff30290 ACPI: MADT (v001 A M I OEMAPIC 0x08000320 MSFT 0x0097) @ 0x3ff30390 ACPI: OEMB (v001 A M I OEMBIOS 0x08000320 MSFT 0x0097) @ 0x3ff40040 ACPI: DSDT (v001 P4P81 P4P81086 0x0086 INTL 0x02002026) @ 0x ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:2 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:2 APIC version 20 ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 4000 (gap: 4000:bfb8) Real-Time Preemption Support (c) Ingo Molnar Built 1 zonelists Kernel command line: root=/dev/hda2 mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 3360.970 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1035212k/1047744k available (1872k kernel code, 12144k reserved, 598k data, 176k init, 130240k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 6668.28 BogoMIPS (lpj=3334144) Security Framework v1.0.0 initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 4400 CPU: After vendor identify, caps: bfebfbff 4400 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 CPU: After all inits, caps: bfebfbff 0080 4400 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. CPU0: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 Booting processor 1/1 eip 2000 Initializing CPU#1 Calibrating delay loop... 6717.44 BogoMIPS (lpj=3358720) CPU: After generic identify, caps: bfebfbff 4400 CPU: After vendor identify, caps: bfebfbff 4400 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 CPU: After all inits, caps: bfebfbff 0080 4400 CPU1: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 Total of 2 processors activated (13385.72 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 checking TSC synchronization across 2 CPUs: passed. spawn_desched_task() desched cpu_callback 3/ ksoftirqd started up. softirq RT prio: 24. desched cpu_callback 2/ desched thread 0 started up. desched cpu_callback 3/0001 desched cpu_callback 2/0001 ksoftirqd started up. softirq RT prio: 24. Brought up 2 CPUs desched thread 1 started up. CPU0 attaching sched-domain: domain 0: span 3 groups: 1 2 domain 1: span 3
Re: [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00
Our first victim!! :-) On Tue, 2005-04-05 at 20:06 +0100, Rui Nuno Capela wrote: I'm having plenty of this on boot, on my SMP/HT desktop (P4/x86), while running RT-V0.7.44-01 (SMP+PREEMPT_RT): BUG: kstopmachine: RT task yield()-ing! See sample dmesg and .config on attach. OTOH, on my laptop (P4/UP), all seems to be clear fine. The kstopmachine is only run on SMP environments, so it won't show up on your UP machine. Is this something to be affraid of? :) If your box is still running, then no. But it's now a chore to remove the yield from this algorithm, since yields have a possibility to deadlock the system. Although in this particular case, it may not be a problem, since the threads that are being waited on are created for other CPUs. But I haven't looked too much into what stop_machine is doing so I can very well be wrong. Thank you for reporting it, we want to weed out all the yields that a RT task may call. -- Steve - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
