enomai <
>>>>> xenomai@xenomai.org> wrote:
>>>>>
>>>>>> Greetings Xenomai list,
>>>>>>
>>>>>>
>>>>>> I have a Linux OE 4.14.85 build with Xenomai 3.1 -next branch, and am
>>>>>> seeing th
ai 3.1 -next branch, and am
> >>>>> seeing this:
> >>>>>
> >>>>> root@ICB-G3L:~ # uname -a
> >>>>> Linux ICB-G3L 4.14.85_C01571-15S01A01.000.zimg+35a84af5b7 #1 SMP Mon
> Feb
> >>>>> 22 20:57:38 UTC 2021 armv7
eetings Xenomai list,
>>>>>
>>>>>
>>>>> I have a Linux OE 4.14.85 build with Xenomai 3.1 -next branch, and am
>>>>> seeing this:
>>>>>
>>>>> root@ICB-G3L:~ # uname -a
>>>>> Linux ICB-G3L
ith Xenomai 3.1 -next branch, and am
>>>> seeing this:
>>>>
>>>> root@ICB-G3L:~ # uname -a
>>>> Linux ICB-G3L 4.14.85_C01571-15S01A01.000.zimg+35a84af5b7 #1 SMP Mon Feb
>>>> 22 20:57:38 UTC 2021 armv7l GN
>>>> U/Linux
>>>&g
-G3L 4.14.85_C01571-15S01A01.000.zimg+35a84af5b7 #1 SMP Mon Feb
>>> 22 20:57:38 UTC 2021 armv7l GN
>>> U/Linux
>>> root@ICB-G3L:~ # smokey --run=posix_mutex
>>> [ 694.433129] [Xenomai] bad syscall <0x197>
>>> posix_mutex OK
>>>
>>
t; I have a Linux OE 4.14.85 build with Xenomai 3.1 -next branch, and am
>> seeing this:
>>
>> root@ICB-G3L:~ # uname -a
>> Linux ICB-G3L 4.14.85_C01571-15S01A01.000.zimg+35a84af5b7 #1 SMP Mon Feb
>> 22 20:57:38 UTC 2021 armv7l GN
>> U/Linux
>> root@ICB-G3L:~ #
uname -a
Linux ICB-G3L 4.14.85_C01571-15S01A01.000.zimg+35a84af5b7 #1 SMP
Mon Feb
22 20:57:38 UTC 2021 armv7l GN
U/Linux
root@ICB-G3L:~ # smokey --run=posix_mutex
[ 694.433129] [Xenomai] bad syscall <0x197>
posix_mutex OK
I found this thread:
http
5S01A01.000.zimg+35a84af5b7 #1 SMP Mon Feb
> 22 20:57:38 UTC 2021 armv7l GN
> U/Linux
> root@ICB-G3L:~ # smokey --run=posix_mutex
> [ 694.433129] [Xenomai] bad syscall <0x197>
> posix_mutex OK
>
> I found this thread:
>
> https://www.mail-archive.com/xenomai@xenom
[ 694.433129] [Xenomai] bad syscall <0x197>
posix_mutex OK
I found this thread:
https://www.mail-archive.com/xenomai@xenomai.org/msg17931.html
But I can't get a clear picture on the proper resolution of this issue,
other than it's related to a non-existent syscall, perhaps glibc