[Xenomai] "RT throttling" issue
JK.Behnke at web.de
Tue Dec 8 11:42:32 CET 2015
> > >> Now I have the following questions
> > >> 1. What is meant by "domain stalled", "current" and
> > >> 2. What is that process having ID "[ 0]"
> > >> 3. How can I tell processes running in secondary mode from
> > >> (just by looking at the priority value?)
> > >>
> > >> Any hint on interpreting my frozen file is appreciated.
> > >
> > > This trace is worthless. To have a meaningful trace, enable
> > > on functions entry (the default when you enable the I-pipe
> > >
> > Do you mean CONFIG_FUNCTION_TRACE?
> I mean CONFIG_IPIPE_TRACE_MCOUNT
I enabled CONFIG_IPIPE_TRACE_MCOUNT=Y and set
to get 256000 lines of backtrace history.
I captured some frozen files, when RT Throttling occurred and during
To me, they look very similar and I am not sure at what functions
I should look at.
The longest delay values (>= 1000us) I observe for the following
They occur every 5..10 ms.
__ipipe_halt_root : delays = 1000us .. 3900us
__ipipe_restore_root_nosync : delays = 1000us .. 3900us
As "__ipipe_halt_root" is called by "default_idle", and the delay
increase (up to 9984 us), when the application is not running, I guess
is actually CPU idle time and not relevant.
"ipipe_root_only" also occasionally has long delay times.
Is ipipe_root_only run when Linux is executing?
Is this critical?
See extract below.
================== start: extract from frozen file
: +func -420045+ 1.443 ipipe_root_only+0x4
: +func -420044 0.260 __ipipe_syscall_root+0x5
: +func -420043 0.200 sys_time+0x5
: +func -420043 0.210 get_seconds+0x3
: +func -420043! 3910.393 ipipe_root_only+0x4
:| +func -416132 0.651 __ipipe_handle_irq+0x5
:| +func -416132 0.340 __ipipe_dispatch_irq+0x9
================== end: extract from frozen file
Any other suggestions where to look at?
Thanks in advance
More information about the Xenomai