Possible Cobalt mqueue issue

Jan Kiszka jan.kiszka at siemens.com
Mon Feb 25 19:56:55 CET 2019


On 25.02.19 19:38, Steve Freyder wrote:
> 
> 
> On 2/25/2019 11:15 AM, Jan Kiszka wrote:
>> On 25.02.19 17:53, Steve Freyder via Xenomai wrote:
>>> Greetings again,
>>>
>>> Recently I have converted my codebase from using Alchemy-based queues 
>>> (rt_queue_xx) to Cobalt (Posix) mqueues for all inter-process communication, 
>>> and using rt_queue queues only for communication between threads in the same 
>>> process.
>>>
>>> This is running on Xenomai 3.0.7 built from -next (our vendor does the 
>>> Xenomai/kernel builds):
>>
>> Was that really 3.0.7, not 3.0.8 or latest stable-3.0.x? There e.g. 
>> https://gitlab.denx.de/Xenomai/xenomai/commit/4924717ec5cbc694afc1b91ba7d525b80901d44d 
>> since 3.0.7, and you backtrace kind of looks familiar /wrt that.
>>
>> Jan
>>
>>>
>>> Linux g3l-36 4.1.18_C01571-15S01-00.002.zimg+83fdace666 #4 SMP Tue Aug 21 
>>> 11:22:31 CDT 2018 armv7l GNU/Linux
> Now that I see that, you're absolutely right and I do apologize for bothering 
> you with this.  After looking at that patch (from October 2018) I do remember 
> when you originally posted it and thinking at the time that I needed to pick it 
> up in a future build.  The build from Aug 21 2018 was 3.0.7 and didn't include 
> your 4924717e fix.  I guess it is time for me to move to a stable-3.0.9 build!

Every testing and reporting is highly appreciated!

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux



More information about the Xenomai mailing list