On Tue, Dec 09, 2014 at 08:49:49PM +0000, Stoidner, Christoph wrote:
>
> Now with the fix from above unfortunately I ran into another problem.
>
> After some undetermined situation nuclues freezes. That means all
> tasks running in primary domain are freezed. In contrast all
> processes and tasks of secondary domain are still running without
> any problem at the same time. The xenomai task states are looking
> normal:
>
> ~ # cat /proc/xenomai/stat
> CPU PID MSW CSW PF STAT %CPU NAME
> 0 0 0 13914 0 00500080 98.8 ROOT
> 0 83 196 196 0 00300380 0.0 DOS4
> 0 82 13 13 0 00300380 0.0 DOS5
>
> I have enabled ipipe traceing to figure out what's happening here
> (see output below, created after tasks have freezed). However I am
> not sure how to interpret that. Does anyone has an idea?
ipipe tracing will not help you, because you have no way to trigger
it at the right time.
Anyway, is not it simply a deadlock in your application ?
Please check that Xenomai timer is still running by checking that
its counter increases in cat /proc/xenomai/irq result.
If Xenomai and Linux timers are shared (I believe they are on
imx28), checking the same thing for Linux timer in /proc/interrupts
is sufficient, Xenomai timer can not possibly be jammed if Linux
timer still ticks.
--
Gilles.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
