Gilles Chanteperdrix wrote:
Jan Kiszka wrote:
> my colleagues and I need some hint where to continue our search for the
> cause of a weird cleanup issue:
> An application of our robotics framework sometimes terminates (though
> successfully) in a way that the system timer IRQ no longer arrives
> afterwards or no re-program takes place anymore. All other Linux IRQs
> are fine (Ethernet, keyboard, etc.). I cannot provide an easy test case
> yet as besides the framework some expensive gyroscope and the 16550A
> driver are involved.
I observed a similar issue when xnpod_stop_timer was called when
shutting down the posix skin. I assumed that the problem was that
xnpod_shutdown already called xnpod_stop_timer, so xnpod_stop_timer (and
in particular xnarch_stop_timer) ended up being called twice.
Err, sorry. Forget about my previous reply: xnarch_stop_timer is _not_
protected by the XNTIMED flag, but only the last part of the
housekeeping chores performed upon stopping the systimer are. IOW, this
is a latent bug, and xnpod_stop_timer should be fixed.
Xenomai-core mailing list