Nicolas BLANCHARD wrote: > Hi ! > > I'm newbie in xenomai world, > I've write an application which make a lot of switch mode > (Primary->secondary ...) > and sometime tasks are block in secondary mode (/proc/xenomai/sched -> > stat X). > (no watchod message in dmesg, it's block in secondary mode). > > I use xenomai 2.2.5, adeos 1.5.02 (same probleme with 2.2.3 et adeos > 1.4) > It' run on x86 (486 vortex 166Mhz). > So, i've write an litle example that failed. It failed on my x86 (in > less than 2 minutes), > but this example run corectly with a pentium 4 or an Amd processor :
How does it fail precisely? Which tasks are stuck? Attach
/proc/xenomai/sched output e.g. Already tried to attach gdb to that
process after the lock-up?
One difference of vortex vs. P4 might be (besides speed) that for the
former Xenomai uses TSC emulation, for the latter the CPU already comes
with this support. You can force the high-end systems into that mode by
compiling the kernel with CONFIG_M586. Or did you use the same kernel
images on all systems?
Your .config would be interesting. You can already check if
CONFIG_INPUT_PCSPKR is set. Must be off for TSC emulation (Xenomai 2.2
doesn't check for this conflict, 2.3 will do so).
>
> #include <sys/mman.h>
> #include <stdio.h>
> #include <signal.h>
> #include <native/task.h>
> #include <string.h>
>
> static int iStop = 0;
> RT_TASK Task_1, Task_2;
> //----------------------------------------------------------------------THREAD
> 1
> void thread_1(void *arg)
> {
> while(1)
> {
> unsigned long overruns;
> int iErr;
>
> iErr = rt_task_wait_period(&overruns);
> if (iErr || overruns)
> printf("Echec wait_period task_1 err %d,
> overruns: %lu\n",iErr,overruns);
Would have been better to attach the program instead of inlining it. :)
>
> //iErr = rt_task_set_mode(T_PRIMARY, 0, NULL);
> if(iErr)
> printf("Echec set_mod Secondary task_1\n");
> printf("r\n");
> if(iStop == 1)
> {
> iErr = rt_task_delete(&Task_1);
> if (iErr )
> printf("Echec delete task_1 err %d\n",
> iErr);
> break;
> }
> }
There is no mode switch in this thread and the second one. Is this not
required to cause the lock-up???
...
>
> If thoses two task have the same priority it looks to not failed,
> perhaps a problem
> with the scheduler in secondary mode when two task comes from primary
> mode ?
> Is it a know probleme with x86 ?
Nope. Fairly unusual. Does the switchtest from the Xenomai test-suite
fail as well?
> Or perhaps a big error in my example ...
Nothing I can see.
>
> Have you an idea ?
> thanks in advance
>
> nicolas blanchard
>
Jan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
