From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <54624F9F.5000207@xenomai.org> Date: Tue, 11 Nov 2014 19:04:15 +0100 From: Philippe Gerum MIME-Version: 1.0 References: <04e5e7e2fab241a5916e4e48f9d9b325@EX132MBOX1B.de2.local> <20141109155351.GH17476@sisyphus.hd.free.fr> <28083d9b9cc34fce9a6d308e8d12fbc6@EX132MBOX1B.de2.local> <20141110124308.GK17476@sisyphus.hd.free.fr> <20141111174652.GK17476@sisyphus.hd.free.fr> In-Reply-To: <20141111174652.GK17476@sisyphus.hd.free.fr> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] "inconsistent lock state" on boot-up List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix , "Stoidner, Christoph" Cc: "xenomai@xenomai.org" On 11/11/2014 06:46 PM, Gilles Chanteperdrix wrote: > On Tue, Nov 11, 2014 at 05:33:55PM +0000, Stoidner, Christoph wrote: >> >> 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! > > You are welcome. As a side note, if you have followed the > discussion, CONFIG_TRACE_IRQFLAGS is broken on ARM, Jan hopes to be > able to fix it, but for the time being, you should disable it, or > you risk to create other issues. > CONFIG_TRACE_IRQFLAGS is currently broken on several architectures with IPIPE enabled. ppc64 certainly is, ppc32 likely, blackfin maybe. I did not check x86 while upgrading to 3.16 yet. -- Philippe.