On Oct 9, 2014 6:16 PM, "Gilles Chanteperdrix" < [email protected]> wrote: > > On 10/09/2014 12:12 PM, GP Orcullo wrote: > > On Thu, Oct 9, 2014 at 6:06 PM, Gilles Chanteperdrix > > <[email protected]> wrote: > >> On 10/09/2014 12:02 PM, GP Orcullo wrote: > >>> On Mon, Oct 6, 2014 at 6:30 AM, Gilles Chanteperdrix > >>> <[email protected]> wrote: > >>>> > >>>> 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. > >>> > >>> One more piece to the puzzle: disabling CONFIG_IPIPE_DEBUG_INTERNAL > >>> causes the system to lockup. > >>> > >> How do you know this is related? > >> > >> -- > >> Gilles. > > > > Sorry, I quoted the wrong message. > > > > If CONFIG_PREEMPT is disabled and CONFIG_IPIPE_DEBUG_INTERNAL is not > > disabled, the system works fine. > > > So, there is a problem, likely in your port with CONFIG_PREEMPT, but > maybe in Xenomai (I need to check, because I am not so sure I tested > xeno-regression-test without CONFIG_PREEMPT). > > And there is a problem in your port without CONFIG_IPIPE_DEBUG_INTERNAL. > This I do not need to check, I have tested Xenomai wihout this option > enabled. > > So, my question is: how do you know the two issues are related? > > -- > Gilles.
I don't know the answer. I'm only looking at the effects and not the cause of the issue. So, where shall I start digging? What's in CONFIG_IPIPE_DEBUG_INTERNAL that would somehow suppress the problem? _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
