Re: [Xenomai] "inconsistent lock state" on boot-up

[Philippe Gerum <rpm@xenomai.org>]

On 11/17/2014 02:10 PM, Gilles Chanteperdrix wrote:
> On Mon, Nov 17, 2014 at 12:49:01PM +0100, Philippe Gerum wrote:
>> On 11/17/2014 11:01 AM, Stoidner, Christoph wrote:
>>>
>>> Hi,
>>>
>>>> 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.
>>>
>>> Now the problem "scheduling while atomic" does not occur anymore within API calls of our own skin. However, after some run-time (about 5 minutes or more) it seems to appear in gatekeeper-thread (see below). 
>>>
>>> What is not clear to me is the ipipe_raise_irq() call in backtrace below. I could not identify any according call from within gatekeeper_thread(). Do I overlook something?
>>>
>>
>> You could match the closest routine to the calling PC value (c00aac84)
>> using add2line on your kernel image.
>>
>> e.g. arm-linux-gnueabihf-addr2line -e vmlinux -a c00aac84
> 
> That would rather be:
> arm-none-linux-gnueabi-addr2line
> 
> imx28 is an armv5 (who said that armv4 and armv5 were no longer in
> circulation ?).
> 
> :-)
> just nitpicking.
> 
> If you have a the multiarch binutils version installed, the default
> addr2line should work as well.
> 

"e.g." precisely stands for this, "to be replaced by the command that
fits". I'm not building for v4/5 these days.

-- 
Philippe.