Hi Gilles, > Also, for the "scheduling while atomic", it may happen if you call > some Linux service which reschedules from primary mode, you can try > enabling I-pipe debugging, and in fact all Xenomai debugging, to try > and catch such mistakes. This is especially important if you are > running a custom skin.
you are completely right, we have implemented our own skin. Using the debugging functionality mentioned above we have identified a function-call that leads to exact the behaviour as described in your post. Hopefully solving that issue solves our application crash. Thanks for your fast and helpful support! Regards, Christoph ________________________________________ Von: Gilles Chanteperdrix <[email protected]> Gesendet: Montag, 10. November 2014 13:43 An: Stoidner, Christoph Cc: [email protected] Betreff: Re: [Xenomai] "inconsistent lock state" on boot-up On Mon, Nov 10, 2014 at 09:08:47AM +0000, Stoidner, Christoph wrote: > > Hi Gilles, > > > Do you have the same message with exactly the same kernel > > configuration, only with CONFIG_XENOMAI and CONFIG_IPIPE disabled? > > When CONFIG_XENOMAI and CONFIG_IPIPE are disabled the message does not > appear on boot-up. > > > Do you have FCSE enabled? If yes, did you try disabling it? same > > with unlocked context switch. > > FCSE is already disabled at all. > > Do you have an idea how to overcome the problem? I am not sure the lockdep message really is a problem. lockdep could be confused by the fact that the hardware interrupts are not off when running the I-pipe, or because we are missing some bit in the I-pipe arm specific code to get it looking at the virtual mask instead of the hardware mask. As for the scheduling while atomic and random segmentation fault, you should use the I-pipe tracer, configure it with enough back trace points, something like 1000 or 10000, and trigger a trace freeze in the kernell code when the problem happens. Also, for the "scheduling while atomic", it may happen if you call some Linux service which reschedules from primary mode, you can try enabling I-pipe debugging, and in fact all Xenomai debugging, to try and catch such mistakes. This is especially important if you are running a custom skin. -- Gilles. _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
