On Mon, Oct 06, 2014 at 06:24:53AM +0800, GP Orcullo wrote:
> On Mon, Oct 6, 2014 at 6:04 AM, Gilles Chanteperdrix
> <[email protected]> wrote:
> > On Mon, Oct 06, 2014 at 06:00:23AM +0800, GP Orcullo wrote:
> >> The cause of the lockups is due to CONFIG_PREEMPT. The board is
> >> running for more than 6 hrs now after disabling it.
> >>
> >> Thanks for all your help!
> >
> > Xenomai runs fine with CONFIG_PREEMPT. The reason why CONFIG_PREEMPT
> > may be an issue is if you are using "preempt_disable" or
> > "preempt_enable", which use current, in a place where you
> > should not (on the context of a kernel-space thread for
> > instance). This happens for instance when using a plain Linux
> > spinlock in real-time code.
> >
> > But this should not happen.
> >
>
> Before disabling CONFIG_PREEMPT, I've been seeing this line:
>
> [ 123.982550] hrtimer: interrupt took 280933 ns
>
> Is this normal?
>
It means that Linux was interrupted by Xenomai during its timer
interrupt, and that Xenomai interrupted it for 280us. This may
happens with switchtest if it has a really long chain of context
switches. If you want to check what happened, enable the I-pipe
tracer, and trigger a trace freeze right before this message.
--
Gilles.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
