Missing asm/fpu/internal.h

Missing asm/fpu/internal.h

[Tamás Paál]

Dear All,

I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
It works fine. I would like to upgrade to a more recent kernel, but I
run into a kernel compilation error very early:


In file included from ./include/asm-generic/xenomai/syscall.h:26,
                 from
./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
                 from ./include/xenomai/pipeline/pipeline.h:12,
                 from ./include/xenomai/cobalt/kernel/lock.h:26,
                 from ./include/xenomai/cobalt/kernel/sched.h:23,
                 from ./arch/x86/include/dovetail/irq.h:12,
                 from kernel/irq/pipeline.c:17:
./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
asm/fpu/internal.h: No such file or directory
   44 | #include <asm/fpu/internal.h>
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
make[1]: *** [scripts/Makefile.build:494: kernel] Error 2


I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
combinations, with the same result.
In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
an internal.h, but I cannot find this file from 5.19 and above. I
believe this is the cause of the error.

Please help me. What am I doing wrong?

Thank you,
Tamas

Re: Missing asm/fpu/internal.h

[Florian Bezdeka]

On Mon, 2023-07-17 at 11:05 +0200, Tamás Paál wrote:
> Dear All,
> 
> I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> It works fine. I would like to upgrade to a more recent kernel, but I
> run into a kernel compilation error very early:
> 
> 
> In file included from ./include/asm-generic/xenomai/syscall.h:26,
>                  from
> ./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
>                  from ./include/xenomai/pipeline/pipeline.h:12,
>                  from ./include/xenomai/cobalt/kernel/lock.h:26,
>                  from ./include/xenomai/cobalt/kernel/sched.h:23,
>                  from ./arch/x86/include/dovetail/irq.h:12,
>                  from kernel/irq/pipeline.c:17:
> ./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
> asm/fpu/internal.h: No such file or directory
>    44 | #include <asm/fpu/internal.h>
>       |          ^~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
> make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
> make[1]: *** [scripts/Makefile.build:494: kernel] Error 2
> 
> 
> I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
> combinations, with the same result.
> In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
> an internal.h, but I cannot find this file from 5.19 and above. I
> believe this is the cause of the error.
> 
> Please help me. What am I doing wrong?

Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
Linux versions you have to use Xenomai from master branch. There is no
3.3 release yet, but we're working on it. We already discussed that
"missing release" in our community call some days ago. There are some
features pending that we would like to integrate. So: stay tuned.

Florian

> 
> Thank you,
> Tamas
> 

Re: Missing asm/fpu/internal.h

[Tamás Paál]

> Dear All,
>
> I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> It works fine. I would like to upgrade to a more recent kernel, but I
> run into a kernel compilation error very early:
>
>
> In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> Linux versions you have to use Xenomai from master branch. There is no
>3.3 release yet, but we're working on it. We already discussed that
>"missing release" in our community call some days ago. There are some
>features pending that we would like to integrate. So: stay tuned.
>
>Florian

Thank you!
Which kernel do you recommend to start working with. 6.1, or 6.4? Is
the current master in a "working shape", or should I wait for a
release?

Thank you very much!
Tamas

Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
júl. 17., H, 11:15):
>
> On Mon, 2023-07-17 at 11:05 +0200, Tamás Paál wrote:
> > Dear All,
> >
> > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > It works fine. I would like to upgrade to a more recent kernel, but I
> > run into a kernel compilation error very early:
> >
> >
> > In file included from ./include/asm-generic/xenomai/syscall.h:26,
> >                  from
> > ./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
> >                  from ./include/xenomai/pipeline/pipeline.h:12,
> >                  from ./include/xenomai/cobalt/kernel/lock.h:26,
> >                  from ./include/xenomai/cobalt/kernel/sched.h:23,
> >                  from ./arch/x86/include/dovetail/irq.h:12,
> >                  from kernel/irq/pipeline.c:17:
> > ./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
> > asm/fpu/internal.h: No such file or directory
> >    44 | #include <asm/fpu/internal.h>
> >       |          ^~~~~~~~~~~~~~~~~~~~
> > compilation terminated.
> > make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
> > make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
> > make[1]: *** [scripts/Makefile.build:494: kernel] Error 2
> >
> >
> > I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
> > combinations, with the same result.
> > In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
> > an internal.h, but I cannot find this file from 5.19 and above. I
> > believe this is the cause of the error.
> >
> > Please help me. What am I doing wrong?
>
> Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> Linux versions you have to use Xenomai from master branch. There is no
> 3.3 release yet, but we're working on it. We already discussed that
> "missing release" in our community call some days ago. There are some
> features pending that we would like to integrate. So: stay tuned.
>
> Florian
>
> >
> > Thank you,
> > Tamas
> >
>

Re: Missing asm/fpu/internal.h

[Florian Bezdeka]

On Mon, 2023-07-17 at 11:36 +0200, Tamás Paál wrote:
> > Dear All,
> > 
> > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > It works fine. I would like to upgrade to a more recent kernel, but I
> > run into a kernel compilation error very early:
> > 
> > 
> > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > Linux versions you have to use Xenomai from master branch. There is no
> > 3.3 release yet, but we're working on it. We already discussed that
> > "missing release" in our community call some days ago. There are some
> > features pending that we would like to integrate. So: stay tuned.
> > 
> > Florian
> 
> Thank you!
> Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> the current master in a "working shape", or should I wait for a
> release?

6.1 is a LTS (Long Term Support) release, so it will stay for some
time, Xenomai support included.

6.4 is just a normal release and will vanish once 6.5. is out. We're
testing that in combination with latest Xenomai already (to make sure
we stay compatible) but we do not plan to support that specific release
over the long run.

Florian

> 
> Thank you very much!
> Tamas
> 
> Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> júl. 17., H, 11:15):
> > 
> > On Mon, 2023-07-17 at 11:05 +0200, Tamás Paál wrote:
> > > Dear All,
> > > 
> > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > run into a kernel compilation error very early:
> > > 
> > > 
> > > In file included from ./include/asm-generic/xenomai/syscall.h:26,
> > >                  from
> > > ./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
> > >                  from ./include/xenomai/pipeline/pipeline.h:12,
> > >                  from ./include/xenomai/cobalt/kernel/lock.h:26,
> > >                  from ./include/xenomai/cobalt/kernel/sched.h:23,
> > >                  from ./arch/x86/include/dovetail/irq.h:12,
> > >                  from kernel/irq/pipeline.c:17:
> > > ./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
> > > asm/fpu/internal.h: No such file or directory
> > >    44 | #include <asm/fpu/internal.h>
> > >       |          ^~~~~~~~~~~~~~~~~~~~
> > > compilation terminated.
> > > make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
> > > make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
> > > make[1]: *** [scripts/Makefile.build:494: kernel] Error 2
> > > 
> > > 
> > > I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
> > > combinations, with the same result.
> > > In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
> > > an internal.h, but I cannot find this file from 5.19 and above. I
> > > believe this is the cause of the error.
> > > 
> > > Please help me. What am I doing wrong?
> > 
> > Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > Linux versions you have to use Xenomai from master branch. There is no
> > 3.3 release yet, but we're working on it. We already discussed that
> > "missing release" in our community call some days ago. There are some
> > features pending that we would like to integrate. So: stay tuned.
> > 
> > Florian
> > 
> > > 
> > > Thank you,
> > > Tamas
> > > 
> > 
> 

Re: Missing asm/fpu/internal.h

[Tamás Paál]

> > > Dear All,
> > >
> > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > run into a kernel compilation error very early:
> > >
> > >
> > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > Linux versions you have to use Xenomai from master branch. There is no
> > > 3.3 release yet, but we're working on it. We already discussed that
> > > "missing release" in our community call some days ago. There are some
> > > features pending that we would like to integrate. So: stay tuned.
> > >
> > > Florian
> >
> > Thank you!
> > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > the current master in a "working shape", or should I wait for a
> > release?
>
> 6.1 is a LTS (Long Term Support) release, so it will stay for some
> time, Xenomai support included.
>
> 6.4 is just a normal release and will vanish once 6.5. is out. We're
> testing that in combination with latest Xenomai already (to make sure
> we stay compatible) but we do not plan to support that specific release
> over the long run.
>
> Florian

Thank you very much!
Tamas

Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
júl. 17., H, 11:46):
>
> On Mon, 2023-07-17 at 11:36 +0200, Tamás Paál wrote:
> > > Dear All,
> > >
> > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > run into a kernel compilation error very early:
> > >
> > >
> > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > Linux versions you have to use Xenomai from master branch. There is no
> > > 3.3 release yet, but we're working on it. We already discussed that
> > > "missing release" in our community call some days ago. There are some
> > > features pending that we would like to integrate. So: stay tuned.
> > >
> > > Florian
> >
> > Thank you!
> > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > the current master in a "working shape", or should I wait for a
> > release?
>
> 6.1 is a LTS (Long Term Support) release, so it will stay for some
> time, Xenomai support included.
>
> 6.4 is just a normal release and will vanish once 6.5. is out. We're
> testing that in combination with latest Xenomai already (to make sure
> we stay compatible) but we do not plan to support that specific release
> over the long run.
>
> Florian
>
> >
> > Thank you very much!
> > Tamas
> >
> > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > júl. 17., H, 11:15):
> > >
> > > On Mon, 2023-07-17 at 11:05 +0200, Tamás Paál wrote:
> > > > Dear All,
> > > >
> > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > run into a kernel compilation error very early:
> > > >
> > > >
> > > > In file included from ./include/asm-generic/xenomai/syscall.h:26,
> > > >                  from
> > > > ./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
> > > >                  from ./include/xenomai/pipeline/pipeline.h:12,
> > > >                  from ./include/xenomai/cobalt/kernel/lock.h:26,
> > > >                  from ./include/xenomai/cobalt/kernel/sched.h:23,
> > > >                  from ./arch/x86/include/dovetail/irq.h:12,
> > > >                  from kernel/irq/pipeline.c:17:
> > > > ./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
> > > > asm/fpu/internal.h: No such file or directory
> > > >    44 | #include <asm/fpu/internal.h>
> > > >       |          ^~~~~~~~~~~~~~~~~~~~
> > > > compilation terminated.
> > > > make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
> > > > make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
> > > > make[1]: *** [scripts/Makefile.build:494: kernel] Error 2
> > > >
> > > >
> > > > I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
> > > > combinations, with the same result.
> > > > In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
> > > > an internal.h, but I cannot find this file from 5.19 and above. I
> > > > believe this is the cause of the error.
> > > >
> > > > Please help me. What am I doing wrong?
> > >
> > > Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > Linux versions you have to use Xenomai from master branch. There is no
> > > 3.3 release yet, but we're working on it. We already discussed that
> > > "missing release" in our community call some days ago. There are some
> > > features pending that we would like to integrate. So: stay tuned.
> > >
> > > Florian
> > >
> > > >
> > > > Thank you,
> > > > Tamas
> > > >
> > >
> >
>

Re: Missing asm/fpu/internal.h

[Tamás Paál]

> > > > Dear All,
> > > >
> > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > run into a kernel compilation error very early:
> > > > >
> > >
> > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > "missing release" in our community call some days ago. There are some
> > > > features pending that we would like to integrate. So: stay tuned.
> > > >
> > > > Florian
> > >
> > > Thank you!
> > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > the current master in a "working shape", or should I wait for a
> > > release?
> > >
> > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > time, Xenomai support included.
> >
> > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > testing that in combination with latest Xenomai already (to make sure
> > we stay compatible) but we do not plan to support that specific release
> > over the long run.
> >
> > Florian
>
> Thank you very much!
> Tamas

I downloaded the latest  Xenomai master branch. I compiled a new
kernel (6.1 and 6.4 behaves the same way) . The xeno-test fails:

./xeno-test: line 100:  1746 Segmentation fault      (core dumped)
$testdir/smokey --run $run_on_vm $keep_going random_alloc_rounds=64
pattern_check_rounds=64
+ start_timesyncd
+ true
+ systemctl start systemd-timesyncd
+ timesyncd_was_running=false
child 1739 returned: exited with status 139

Am I doing something wrong?
Thank you,
Tamas

Tamás Paál <paal.tam@gmail.com> ezt írta (időpont: 2023. júl. 17., H, 11:49):
>
> > > > Dear All,
> > > >
> > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > run into a kernel compilation error very early:
> > > >
> > > >
> > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > "missing release" in our community call some days ago. There are some
> > > > features pending that we would like to integrate. So: stay tuned.
> > > >
> > > > Florian
> > >
> > > Thank you!
> > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > the current master in a "working shape", or should I wait for a
> > > release?
> >
> > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > time, Xenomai support included.
> >
> > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > testing that in combination with latest Xenomai already (to make sure
> > we stay compatible) but we do not plan to support that specific release
> > over the long run.
> >
> > Florian
>
> Thank you very much!
> Tamas
>
> Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> júl. 17., H, 11:46):
> >
> > On Mon, 2023-07-17 at 11:36 +0200, Tamás Paál wrote:
> > > > Dear All,
> > > >
> > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > run into a kernel compilation error very early:
> > > >
> > > >
> > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > "missing release" in our community call some days ago. There are some
> > > > features pending that we would like to integrate. So: stay tuned.
> > > >
> > > > Florian
> > >
> > > Thank you!
> > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > the current master in a "working shape", or should I wait for a
> > > release?
> >
> > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > time, Xenomai support included.
> >
> > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > testing that in combination with latest Xenomai already (to make sure
> > we stay compatible) but we do not plan to support that specific release
> > over the long run.
> >
> > Florian
> >
> > >
> > > Thank you very much!
> > > Tamas
> > >
> > > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > > júl. 17., H, 11:15):
> > > >
> > > > On Mon, 2023-07-17 at 11:05 +0200, Tamás Paál wrote:
> > > > > Dear All,
> > > > >
> > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > run into a kernel compilation error very early:
> > > > >
> > > > >
> > > > > In file included from ./include/asm-generic/xenomai/syscall.h:26,
> > > > >                  from
> > > > > ./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
> > > > >                  from ./include/xenomai/pipeline/pipeline.h:12,
> > > > >                  from ./include/xenomai/cobalt/kernel/lock.h:26,
> > > > >                  from ./include/xenomai/cobalt/kernel/sched.h:23,
> > > > >                  from ./arch/x86/include/dovetail/irq.h:12,
> > > > >                  from kernel/irq/pipeline.c:17:
> > > > > ./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
> > > > > asm/fpu/internal.h: No such file or directory
> > > > >    44 | #include <asm/fpu/internal.h>
> > > > >       |          ^~~~~~~~~~~~~~~~~~~~
> > > > > compilation terminated.
> > > > > make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
> > > > > make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
> > > > > make[1]: *** [scripts/Makefile.build:494: kernel] Error 2
> > > > >
> > > > >
> > > > > I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
> > > > > combinations, with the same result.
> > > > > In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
> > > > > an internal.h, but I cannot find this file from 5.19 and above. I
> > > > > believe this is the cause of the error.
> > > > >
> > > > > Please help me. What am I doing wrong?
> > > >
> > > > Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > "missing release" in our community call some days ago. There are some
> > > > features pending that we would like to integrate. So: stay tuned.
> > > >
> > > > Florian
> > > >
> > > > >
> > > > > Thank you,
> > > > > Tamas
> > > > >
> > > >
> > >
> >

Re: Missing asm/fpu/internal.h

[Florian Bezdeka]

On Mon, 2023-07-17 at 16:51 +0200, Tamás Paál wrote:
> > > > > Dear All,
> > > > > 
> > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > run into a kernel compilation error very early:
> > > > > > 
> > > > 
> > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > "missing release" in our community call some days ago. There are some
> > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > 
> > > > > Florian
> > > > 
> > > > Thank you!
> > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > the current master in a "working shape", or should I wait for a
> > > > release?
> > > > 
> > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > time, Xenomai support included.
> > > 
> > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > testing that in combination with latest Xenomai already (to make sure
> > > we stay compatible) but we do not plan to support that specific release
> > > over the long run.
> > > 
> > > Florian
> > 
> > Thank you very much!
> > Tamas
> 
> I downloaded the latest  Xenomai master branch. I compiled a new
> kernel (6.1 and 6.4 behaves the same way) . The xeno-test fails:
> 
> ./xeno-test: line 100:  1746 Segmentation fault      (core dumped)
> $testdir/smokey --run $run_on_vm $keep_going random_alloc_rounds=64
> pattern_check_rounds=64
> + start_timesyncd
> + true
> + systemctl start systemd-timesyncd
> + timesyncd_was_running=false
> child 1739 returned: exited with status 139
> 
> Am I doing something wrong?
> Thank you,
> Tamas

The CI runs that we did on this versions look OK, so I think it's a
problem in your setup. Make sure you don't try to run an older (3.2.x)
testsuite linked against up to date Xenomai libraries (or the other way
around).

Maybe something got screwed up while testing all those different
versions?

The segfault happens when trying to run the smokey testsuite. Is it a
single test that fails, or basically all of them? You may limit the
number of tests to be executed by "smokey --run=<list of test names>"

Florian

> 
> Tamás Paál <paal.tam@gmail.com> ezt írta (időpont: 2023. júl. 17., H, 11:49):
> > 
> > > > > Dear All,
> > > > > 
> > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > run into a kernel compilation error very early:
> > > > > 
> > > > > 
> > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > "missing release" in our community call some days ago. There are some
> > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > 
> > > > > Florian
> > > > 
> > > > Thank you!
> > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > the current master in a "working shape", or should I wait for a
> > > > release?
> > > 
> > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > time, Xenomai support included.
> > > 
> > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > testing that in combination with latest Xenomai already (to make sure
> > > we stay compatible) but we do not plan to support that specific release
> > > over the long run.
> > > 
> > > Florian
> > 
> > Thank you very much!
> > Tamas
> > 
> > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > júl. 17., H, 11:46):
> > > 
> > > On Mon, 2023-07-17 at 11:36 +0200, Tamás Paál wrote:
> > > > > Dear All,
> > > > > 
> > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > run into a kernel compilation error very early:
> > > > > 
> > > > > 
> > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > "missing release" in our community call some days ago. There are some
> > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > 
> > > > > Florian
> > > > 
> > > > Thank you!
> > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > the current master in a "working shape", or should I wait for a
> > > > release?
> > > 
> > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > time, Xenomai support included.
> > > 
> > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > testing that in combination with latest Xenomai already (to make sure
> > > we stay compatible) but we do not plan to support that specific release
> > > over the long run.
> > > 
> > > Florian
> > > 
> > > > 
> > > > Thank you very much!
> > > > Tamas
> > > > 
> > > > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > > > júl. 17., H, 11:15):
> > > > > 
> > > > > On Mon, 2023-07-17 at 11:05 +0200, Tamás Paál wrote:
> > > > > > Dear All,
> > > > > > 
> > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > run into a kernel compilation error very early:
> > > > > > 
> > > > > > 
> > > > > > In file included from ./include/asm-generic/xenomai/syscall.h:26,
> > > > > >                  from
> > > > > > ./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
> > > > > >                  from ./include/xenomai/pipeline/pipeline.h:12,
> > > > > >                  from ./include/xenomai/cobalt/kernel/lock.h:26,
> > > > > >                  from ./include/xenomai/cobalt/kernel/sched.h:23,
> > > > > >                  from ./arch/x86/include/dovetail/irq.h:12,
> > > > > >                  from kernel/irq/pipeline.c:17:
> > > > > > ./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
> > > > > > asm/fpu/internal.h: No such file or directory
> > > > > >    44 | #include <asm/fpu/internal.h>
> > > > > >       |          ^~~~~~~~~~~~~~~~~~~~
> > > > > > compilation terminated.
> > > > > > make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
> > > > > > make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
> > > > > > make[1]: *** [scripts/Makefile.build:494: kernel] Error 2
> > > > > > 
> > > > > > 
> > > > > > I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
> > > > > > combinations, with the same result.
> > > > > > In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
> > > > > > an internal.h, but I cannot find this file from 5.19 and above. I
> > > > > > believe this is the cause of the error.
> > > > > > 
> > > > > > Please help me. What am I doing wrong?
> > > > > 
> > > > > Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > "missing release" in our community call some days ago. There are some
> > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > 
> > > > > Florian
> > > > > 
> > > > > > 
> > > > > > Thank you,
> > > > > > Tamas
> > > > > > 
> > > > > 
> > > > 
> > > 
> 

Re: Missing asm/fpu/internal.h

[Tamás Paál]

>The CI runs that we did on this versions look OK, so I think it's a
> problem in your setup. Make sure you don't try to run an older (3.2.x)
> testsuite linked against up to date Xenomai libraries (or the other way
> around).
>
> Maybe something got screwed up while testing all those different
> versions?
>
> The segfault happens when trying to run the smokey testsuite. Is it a
> single test that fails, or basically all of them? You may limit the
> number of tests to be executed by "smokey --run=<list of test names>"

I renamed the /usr/xenomai directory of the old 3.2.x compilation. I
am sure that the current /usr/xenomai directory contains the output of
the last build, that is the current master.
A lot of tests are ok. This is the full output of the xeno-test procedure:

Started child 8092: /bin/bash /usr/xenomai/bin/xeno-test-run-wrapper ./xeno-test
++ echo 0
++ testdir=/usr/xenomai/bin
++ which systemctl
++ systemctl is-active --quiet systemd-timesyncd
++ timesyncd_was_running=true
++ systemctl stop systemd-timesyncd
++ /usr/xenomai/bin/smokey --run random_alloc_rounds=64 pattern_check_rounds=64
arith OK
bufp skipped (no kernel support)
can skipped (no kernel support)
cpu_affinity skipped (no kernel support)
fpu_stress OK
gdb OK
iddp skipped (no kernel support)
leaks OK
memory_coreheap OK
memory_heapmem OK
memory_tlsf OK
net_packet_dgram OK
net_packet_raw OK
net_udp OK
posix_clock OK
posix_cond OK
posix_fork OK
posix_mutex OK
posix_select OK
rtdm skipped (no kernel support)
sched_quota skipped (no kernel support)
sched_tp skipped (no kernel support)
setsched OK
sigdebug skipped (no kernel support)
timerfd OK
tsc OK
vdso_access OK
xddp skipped (no kernel support)
y2038: sizeof(long) = 8, sizeof(time_t) = 8
syscall-tests.c:1027, socket(AF_RTIPC, SOCK_DGRAM, IPCPROTO_XDDP):
Address family not supported by protocol
recvmmsg64: skipped. (no kernel support)
syscall-tests.c:1503, socket(AF_RTIPC, SOCK_DGRAM, IPCPROTO_XDDP):
Address family not supported by protocol
pselect64: skipped timeout write back test
y2038 OK
memory_pshared OK
x86io OK
./xeno-test: line 100:  8099 Segmentation fault      (core dumped)
$testdir/smokey --run $run_on_vm $keep_going random_alloc_rounds=64
pattern_check_rounds=64
+ start_timesyncd
+ true
+ systemctl start systemd-timesyncd
+ timesyncd_was_running=false
child 8092 returned: exited with status 139

Maybe I prepared the kernel in a wrong way? I did it this way:

/usr/src/xenomai-master/scripts/prepare-kernel.sh --arch=x86
--linux=/usr/src/linux-dovetail-v6.1.y-dovetail

Should I use --arch=x86_64 instead?

Thank you,
Tamas

Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
júl. 18., K, 8:44):
>
> On Mon, 2023-07-17 at 16:51 +0200, Tamás Paál wrote:
> > > > > > Dear All,
> > > > > >
> > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > run into a kernel compilation error very early:
> > > > > > >
> > > > >
> > > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > "missing release" in our community call some days ago. There are some
> > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > >
> > > > > > Florian
> > > > >
> > > > > Thank you!
> > > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > > the current master in a "working shape", or should I wait for a
> > > > > release?
> > > > >
> > > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > > time, Xenomai support included.
> > > >
> > > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > > testing that in combination with latest Xenomai already (to make sure
> > > > we stay compatible) but we do not plan to support that specific release
> > > > over the long run.
> > > >
> > > > Florian
> > >
> > > Thank you very much!
> > > Tamas
> >
> > I downloaded the latest  Xenomai master branch. I compiled a new
> > kernel (6.1 and 6.4 behaves the same way) . The xeno-test fails:
> >
> > ./xeno-test: line 100:  1746 Segmentation fault      (core dumped)
> > $testdir/smokey --run $run_on_vm $keep_going random_alloc_rounds=64
> > pattern_check_rounds=64
> > + start_timesyncd
> > + true
> > + systemctl start systemd-timesyncd
> > + timesyncd_was_running=false
> > child 1739 returned: exited with status 139
> >
> > Am I doing something wrong?
> > Thank you,
> > Tamas
>
> The CI runs that we did on this versions look OK, so I think it's a
> problem in your setup. Make sure you don't try to run an older (3.2.x)
> testsuite linked against up to date Xenomai libraries (or the other way
> around).
>
> Maybe something got screwed up while testing all those different
> versions?
>
> The segfault happens when trying to run the smokey testsuite. Is it a
> single test that fails, or basically all of them? You may limit the
> number of tests to be executed by "smokey --run=<list of test names>"
>
> Florian
>
> >
> > Tamás Paál <paal.tam@gmail.com> ezt írta (időpont: 2023. júl. 17., H, 11:49):
> > >
> > > > > > Dear All,
> > > > > >
> > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > run into a kernel compilation error very early:
> > > > > >
> > > > > >
> > > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > "missing release" in our community call some days ago. There are some
> > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > >
> > > > > > Florian
> > > > >
> > > > > Thank you!
> > > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > > the current master in a "working shape", or should I wait for a
> > > > > release?
> > > >
> > > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > > time, Xenomai support included.
> > > >
> > > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > > testing that in combination with latest Xenomai already (to make sure
> > > > we stay compatible) but we do not plan to support that specific release
> > > > over the long run.
> > > >
> > > > Florian
> > >
> > > Thank you very much!
> > > Tamas
> > >
> > > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > > júl. 17., H, 11:46):
> > > >
> > > > On Mon, 2023-07-17 at 11:36 +0200, Tamás Paál wrote:
> > > > > > Dear All,
> > > > > >
> > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > run into a kernel compilation error very early:
> > > > > >
> > > > > >
> > > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > "missing release" in our community call some days ago. There are some
> > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > >
> > > > > > Florian
> > > > >
> > > > > Thank you!
> > > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > > the current master in a "working shape", or should I wait for a
> > > > > release?
> > > >
> > > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > > time, Xenomai support included.
> > > >
> > > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > > testing that in combination with latest Xenomai already (to make sure
> > > > we stay compatible) but we do not plan to support that specific release
> > > > over the long run.
> > > >
> > > > Florian
> > > >
> > > > >
> > > > > Thank you very much!
> > > > > Tamas
> > > > >
> > > > > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > > > > júl. 17., H, 11:15):
> > > > > >
> > > > > > On Mon, 2023-07-17 at 11:05 +0200, Tamás Paál wrote:
> > > > > > > Dear All,
> > > > > > >
> > > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > > run into a kernel compilation error very early:
> > > > > > >
> > > > > > >
> > > > > > > In file included from ./include/asm-generic/xenomai/syscall.h:26,
> > > > > > >                  from
> > > > > > > ./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
> > > > > > >                  from ./include/xenomai/pipeline/pipeline.h:12,
> > > > > > >                  from ./include/xenomai/cobalt/kernel/lock.h:26,
> > > > > > >                  from ./include/xenomai/cobalt/kernel/sched.h:23,
> > > > > > >                  from ./arch/x86/include/dovetail/irq.h:12,
> > > > > > >                  from kernel/irq/pipeline.c:17:
> > > > > > > ./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
> > > > > > > asm/fpu/internal.h: No such file or directory
> > > > > > >    44 | #include <asm/fpu/internal.h>
> > > > > > >       |          ^~~~~~~~~~~~~~~~~~~~
> > > > > > > compilation terminated.
> > > > > > > make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
> > > > > > > make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
> > > > > > > make[1]: *** [scripts/Makefile.build:494: kernel] Error 2
> > > > > > >
> > > > > > >
> > > > > > > I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
> > > > > > > combinations, with the same result.
> > > > > > > In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
> > > > > > > an internal.h, but I cannot find this file from 5.19 and above. I
> > > > > > > believe this is the cause of the error.
> > > > > > >
> > > > > > > Please help me. What am I doing wrong?
> > > > > >
> > > > > > Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > "missing release" in our community call some days ago. There are some
> > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > >
> > > > > > Florian
> > > > > >
> > > > > > >
> > > > > > > Thank you,
> > > > > > > Tamas
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
>

Re: Missing asm/fpu/internal.h

[Florian Bezdeka]

On Tue, 2023-07-18 at 09:49 +0200, Tamás Paál wrote:
> > The CI runs that we did on this versions look OK, so I think it's a
> > problem in your setup. Make sure you don't try to run an older (3.2.x)
> > testsuite linked against up to date Xenomai libraries (or the other way
> > around).
> > 
> > Maybe something got screwed up while testing all those different
> > versions?
> > 
> > The segfault happens when trying to run the smokey testsuite. Is it a
> > single test that fails, or basically all of them? You may limit the
> > number of tests to be executed by "smokey --run=<list of test names>"
> 
> I renamed the /usr/xenomai directory of the old 3.2.x compilation. I
> am sure that the current /usr/xenomai directory contains the output of
> the last build, that is the current master.
> A lot of tests are ok. This is the full output of the xeno-test procedure:
> 
> Started child 8092: /bin/bash /usr/xenomai/bin/xeno-test-run-wrapper ./xeno-test
> ++ echo 0
> ++ testdir=/usr/xenomai/bin
> ++ which systemctl
> ++ systemctl is-active --quiet systemd-timesyncd
> ++ timesyncd_was_running=true
> ++ systemctl stop systemd-timesyncd
> ++ /usr/xenomai/bin/smokey --run random_alloc_rounds=64 pattern_check_rounds=64
> arith OK
> bufp skipped (no kernel support)
> can skipped (no kernel support)
> cpu_affinity skipped (no kernel support)
> fpu_stress OK
> gdb OK
> iddp skipped (no kernel support)
> leaks OK
> memory_coreheap OK
> memory_heapmem OK
> memory_tlsf OK
> net_packet_dgram OK
> net_packet_raw OK
> net_udp OK
> posix_clock OK
> posix_cond OK
> posix_fork OK
> posix_mutex OK
> posix_select OK
> rtdm skipped (no kernel support)
> sched_quota skipped (no kernel support)
> sched_tp skipped (no kernel support)
> setsched OK
> sigdebug skipped (no kernel support)
> timerfd OK
> tsc OK
> vdso_access OK
> xddp skipped (no kernel support)
> y2038: sizeof(long) = 8, sizeof(time_t) = 8
> syscall-tests.c:1027, socket(AF_RTIPC, SOCK_DGRAM, IPCPROTO_XDDP):
> Address family not supported by protocol
> recvmmsg64: skipped. (no kernel support)
> syscall-tests.c:1503, socket(AF_RTIPC, SOCK_DGRAM, IPCPROTO_XDDP):
> Address family not supported by protocol
> pselect64: skipped timeout write back test
> y2038 OK
> memory_pshared OK
> x86io OK
> ./xeno-test: line 100:  8099 Segmentation fault      (core dumped)
> $testdir/smokey --run $run_on_vm $keep_going random_alloc_rounds=64
> pattern_check_rounds=64
> + start_timesyncd
> + true
> + systemctl start systemd-timesyncd
> + timesyncd_was_running=false
> child 8092 returned: exited with status 139

I guess it's the dlopen test that fails here. Could you please confirm
that by running "smokey --run=dlopen" ?

Seems the test infrastructure is unable to locate some binaries that
should be located inside the XENO_TEST_DIR, that seems to fail and then
we crash... Might be a bug triggered by an invalid "test environment".

I will try to reproduce during my next Xenomai time slot ;-)

Florian

> 
> Maybe I prepared the kernel in a wrong way? I did it this way:
> 
> /usr/src/xenomai-master/scripts/prepare-kernel.sh --arch=x86
> --linux=/usr/src/linux-dovetail-v6.1.y-dovetail
> 
> Should I use --arch=x86_64 instead?
> 
> Thank you,
> Tamas
> 
> Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> júl. 18., K, 8:44):
> > 
> > On Mon, 2023-07-17 at 16:51 +0200, Tamás Paál wrote:
> > > > > > > Dear All,
> > > > > > > 
> > > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > > run into a kernel compilation error very early:
> > > > > > > > 
> > > > > > 
> > > > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > > "missing release" in our community call some days ago. There are some
> > > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > > > 
> > > > > > > Florian
> > > > > > 
> > > > > > Thank you!
> > > > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > > > the current master in a "working shape", or should I wait for a
> > > > > > release?
> > > > > > 
> > > > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > > > time, Xenomai support included.
> > > > > 
> > > > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > > > testing that in combination with latest Xenomai already (to make sure
> > > > > we stay compatible) but we do not plan to support that specific release
> > > > > over the long run.
> > > > > 
> > > > > Florian
> > > > 
> > > > Thank you very much!
> > > > Tamas
> > > 
> > > I downloaded the latest  Xenomai master branch. I compiled a new
> > > kernel (6.1 and 6.4 behaves the same way) . The xeno-test fails:
> > > 
> > > ./xeno-test: line 100:  1746 Segmentation fault      (core dumped)
> > > $testdir/smokey --run $run_on_vm $keep_going random_alloc_rounds=64
> > > pattern_check_rounds=64
> > > + start_timesyncd
> > > + true
> > > + systemctl start systemd-timesyncd
> > > + timesyncd_was_running=false
> > > child 1739 returned: exited with status 139
> > > 
> > > Am I doing something wrong?
> > > Thank you,
> > > Tamas
> > 
> > The CI runs that we did on this versions look OK, so I think it's a
> > problem in your setup. Make sure you don't try to run an older (3.2.x)
> > testsuite linked against up to date Xenomai libraries (or the other way
> > around).
> > 
> > Maybe something got screwed up while testing all those different
> > versions?
> > 
> > The segfault happens when trying to run the smokey testsuite. Is it a
> > single test that fails, or basically all of them? You may limit the
> > number of tests to be executed by "smokey --run=<list of test names>"
> > 
> > Florian
> > 
> > > 
> > > Tamás Paál <paal.tam@gmail.com> ezt írta (időpont: 2023. júl. 17., H, 11:49):
> > > > 
> > > > > > > Dear All,
> > > > > > > 
> > > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > > run into a kernel compilation error very early:
> > > > > > > 
> > > > > > > 
> > > > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > > "missing release" in our community call some days ago. There are some
> > > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > > > 
> > > > > > > Florian
> > > > > > 
> > > > > > Thank you!
> > > > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > > > the current master in a "working shape", or should I wait for a
> > > > > > release?
> > > > > 
> > > > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > > > time, Xenomai support included.
> > > > > 
> > > > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > > > testing that in combination with latest Xenomai already (to make sure
> > > > > we stay compatible) but we do not plan to support that specific release
> > > > > over the long run.
> > > > > 
> > > > > Florian
> > > > 
> > > > Thank you very much!
> > > > Tamas
> > > > 
> > > > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > > > júl. 17., H, 11:46):
> > > > > 
> > > > > On Mon, 2023-07-17 at 11:36 +0200, Tamás Paál wrote:
> > > > > > > Dear All,
> > > > > > > 
> > > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > > run into a kernel compilation error very early:
> > > > > > > 
> > > > > > > 
> > > > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > > "missing release" in our community call some days ago. There are some
> > > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > > > 
> > > > > > > Florian
> > > > > > 
> > > > > > Thank you!
> > > > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > > > the current master in a "working shape", or should I wait for a
> > > > > > release?
> > > > > 
> > > > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > > > time, Xenomai support included.
> > > > > 
> > > > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > > > testing that in combination with latest Xenomai already (to make sure
> > > > > we stay compatible) but we do not plan to support that specific release
> > > > > over the long run.
> > > > > 
> > > > > Florian
> > > > > 
> > > > > > 
> > > > > > Thank you very much!
> > > > > > Tamas
> > > > > > 
> > > > > > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > > > > > júl. 17., H, 11:15):
> > > > > > > 
> > > > > > > On Mon, 2023-07-17 at 11:05 +0200, Tamás Paál wrote:
> > > > > > > > Dear All,
> > > > > > > > 
> > > > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > > > run into a kernel compilation error very early:
> > > > > > > > 
> > > > > > > > 
> > > > > > > > In file included from ./include/asm-generic/xenomai/syscall.h:26,
> > > > > > > >                  from
> > > > > > > > ./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
> > > > > > > >                  from ./include/xenomai/pipeline/pipeline.h:12,
> > > > > > > >                  from ./include/xenomai/cobalt/kernel/lock.h:26,
> > > > > > > >                  from ./include/xenomai/cobalt/kernel/sched.h:23,
> > > > > > > >                  from ./arch/x86/include/dovetail/irq.h:12,
> > > > > > > >                  from kernel/irq/pipeline.c:17:
> > > > > > > > ./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
> > > > > > > > asm/fpu/internal.h: No such file or directory
> > > > > > > >    44 | #include <asm/fpu/internal.h>
> > > > > > > >       |          ^~~~~~~~~~~~~~~~~~~~
> > > > > > > > compilation terminated.
> > > > > > > > make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
> > > > > > > > make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
> > > > > > > > make[1]: *** [scripts/Makefile.build:494: kernel] Error 2
> > > > > > > > 
> > > > > > > > 
> > > > > > > > I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
> > > > > > > > combinations, with the same result.
> > > > > > > > In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
> > > > > > > > an internal.h, but I cannot find this file from 5.19 and above. I
> > > > > > > > believe this is the cause of the error.
> > > > > > > > 
> > > > > > > > Please help me. What am I doing wrong?
> > > > > > > 
> > > > > > > Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > > "missing release" in our community call some days ago. There are some
> > > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > > > 
> > > > > > > Florian
> > > > > > > 
> > > > > > > > 
> > > > > > > > Thank you,
> > > > > > > > Tamas
> > > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > 
> > > 
> > 
> 

Re: Missing asm/fpu/internal.h

[Tamás Paál]

> I guess it's the dlopen test that fails here. Could you please confirm
> that by running "smokey --run=dlopen" ?
>
> Seems the test infrastructure is unable to locate some binaries that
> should be located inside the XENO_TEST_DIR, that seems to fail and then
> we crash... Might be a bug triggered by an invalid "test environment".
>
> I will try to reproduce during my next Xenomai time slot ;-)

I tried to execute the command directly as a shell command, or
modified the xeno-test script and execute it that way. Both returned
the same result:

++ echo 0
++ testdir=/usr/xenomai/bin
++ which systemctl
++ systemctl is-active --quiet systemd-timesyncd
++ timesyncd_was_running=true
++ systemctl stop systemd-timesyncd
++ /usr/xenomai/bin/smokey --run=dlopen random_alloc_rounds=64
pattern_check_rounds=64
   0"002.340| WARNING: [smokey] invalid test range in dlopen
   0"002.365| WARNING: [smokey] no test selected
   0"002.375| WARNING: [main] setup call smokey failed
   0"002.385| BUG in __xenomai_init(): [main] initialization failed, EINVAL
+ start_timesyncd
+ true
+ systemctl start systemd-timesyncd
+ timesyncd_was_running=false
child 2268 returned: exited with status 1

Tamas

Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
júl. 18., K, 16:02):
>
> On Tue, 2023-07-18 at 09:49 +0200, Tamás Paál wrote:
> > > The CI runs that we did on this versions look OK, so I think it's a
> > > problem in your setup. Make sure you don't try to run an older (3.2.x)
> > > testsuite linked against up to date Xenomai libraries (or the other way
> > > around).
> > >
> > > Maybe something got screwed up while testing all those different
> > > versions?
> > >
> > > The segfault happens when trying to run the smokey testsuite. Is it a
> > > single test that fails, or basically all of them? You may limit the
> > > number of tests to be executed by "smokey --run=<list of test names>"
> >
> > I renamed the /usr/xenomai directory of the old 3.2.x compilation. I
> > am sure that the current /usr/xenomai directory contains the output of
> > the last build, that is the current master.
> > A lot of tests are ok. This is the full output of the xeno-test procedure:
> >
> > Started child 8092: /bin/bash /usr/xenomai/bin/xeno-test-run-wrapper ./xeno-test
> > ++ echo 0
> > ++ testdir=/usr/xenomai/bin
> > ++ which systemctl
> > ++ systemctl is-active --quiet systemd-timesyncd
> > ++ timesyncd_was_running=true
> > ++ systemctl stop systemd-timesyncd
> > ++ /usr/xenomai/bin/smokey --run random_alloc_rounds=64 pattern_check_rounds=64
> > arith OK
> > bufp skipped (no kernel support)
> > can skipped (no kernel support)
> > cpu_affinity skipped (no kernel support)
> > fpu_stress OK
> > gdb OK
> > iddp skipped (no kernel support)
> > leaks OK
> > memory_coreheap OK
> > memory_heapmem OK
> > memory_tlsf OK
> > net_packet_dgram OK
> > net_packet_raw OK
> > net_udp OK
> > posix_clock OK
> > posix_cond OK
> > posix_fork OK
> > posix_mutex OK
> > posix_select OK
> > rtdm skipped (no kernel support)
> > sched_quota skipped (no kernel support)
> > sched_tp skipped (no kernel support)
> > setsched OK
> > sigdebug skipped (no kernel support)
> > timerfd OK
> > tsc OK
> > vdso_access OK
> > xddp skipped (no kernel support)
> > y2038: sizeof(long) = 8, sizeof(time_t) = 8
> > syscall-tests.c:1027, socket(AF_RTIPC, SOCK_DGRAM, IPCPROTO_XDDP):
> > Address family not supported by protocol
> > recvmmsg64: skipped. (no kernel support)
> > syscall-tests.c:1503, socket(AF_RTIPC, SOCK_DGRAM, IPCPROTO_XDDP):
> > Address family not supported by protocol
> > pselect64: skipped timeout write back test
> > y2038 OK
> > memory_pshared OK
> > x86io OK
> > ./xeno-test: line 100:  8099 Segmentation fault      (core dumped)
> > $testdir/smokey --run $run_on_vm $keep_going random_alloc_rounds=64
> > pattern_check_rounds=64
> > + start_timesyncd
> > + true
> > + systemctl start systemd-timesyncd
> > + timesyncd_was_running=false
> > child 8092 returned: exited with status 139
>
> I guess it's the dlopen test that fails here. Could you please confirm
> that by running "smokey --run=dlopen" ?
>
> Seems the test infrastructure is unable to locate some binaries that
> should be located inside the XENO_TEST_DIR, that seems to fail and then
> we crash... Might be a bug triggered by an invalid "test environment".
>
> I will try to reproduce during my next Xenomai time slot ;-)
>
> Florian
>
> >
> > Maybe I prepared the kernel in a wrong way? I did it this way:
> >
> > /usr/src/xenomai-master/scripts/prepare-kernel.sh --arch=x86
> > --linux=/usr/src/linux-dovetail-v6.1.y-dovetail
> >
> > Should I use --arch=x86_64 instead?
> >
> > Thank you,
> > Tamas
> >
> > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > júl. 18., K, 8:44):
> > >
> > > On Mon, 2023-07-17 at 16:51 +0200, Tamás Paál wrote:
> > > > > > > > Dear All,
> > > > > > > >
> > > > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > > > run into a kernel compilation error very early:
> > > > > > > > >
> > > > > > >
> > > > > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > > > "missing release" in our community call some days ago. There are some
> > > > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > > > >
> > > > > > > > Florian
> > > > > > >
> > > > > > > Thank you!
> > > > > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > > > > the current master in a "working shape", or should I wait for a
> > > > > > > release?
> > > > > > >
> > > > > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > > > > time, Xenomai support included.
> > > > > >
> > > > > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > > > > testing that in combination with latest Xenomai already (to make sure
> > > > > > we stay compatible) but we do not plan to support that specific release
> > > > > > over the long run.
> > > > > >
> > > > > > Florian
> > > > >
> > > > > Thank you very much!
> > > > > Tamas
> > > >
> > > > I downloaded the latest  Xenomai master branch. I compiled a new
> > > > kernel (6.1 and 6.4 behaves the same way) . The xeno-test fails:
> > > >
> > > > ./xeno-test: line 100:  1746 Segmentation fault      (core dumped)
> > > > $testdir/smokey --run $run_on_vm $keep_going random_alloc_rounds=64
> > > > pattern_check_rounds=64
> > > > + start_timesyncd
> > > > + true
> > > > + systemctl start systemd-timesyncd
> > > > + timesyncd_was_running=false
> > > > child 1739 returned: exited with status 139
> > > >
> > > > Am I doing something wrong?
> > > > Thank you,
> > > > Tamas
> > >
> > > The CI runs that we did on this versions look OK, so I think it's a
> > > problem in your setup. Make sure you don't try to run an older (3.2.x)
> > > testsuite linked against up to date Xenomai libraries (or the other way
> > > around).
> > >
> > > Maybe something got screwed up while testing all those different
> > > versions?
> > >
> > > The segfault happens when trying to run the smokey testsuite. Is it a
> > > single test that fails, or basically all of them? You may limit the
> > > number of tests to be executed by "smokey --run=<list of test names>"
> > >
> > > Florian
> > >
> > > >
> > > > Tamás Paál <paal.tam@gmail.com> ezt írta (időpont: 2023. júl. 17., H, 11:49):
> > > > >
> > > > > > > > Dear All,
> > > > > > > >
> > > > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > > > run into a kernel compilation error very early:
> > > > > > > >
> > > > > > > >
> > > > > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > > > "missing release" in our community call some days ago. There are some
> > > > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > > > >
> > > > > > > > Florian
> > > > > > >
> > > > > > > Thank you!
> > > > > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > > > > the current master in a "working shape", or should I wait for a
> > > > > > > release?
> > > > > >
> > > > > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > > > > time, Xenomai support included.
> > > > > >
> > > > > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > > > > testing that in combination with latest Xenomai already (to make sure
> > > > > > we stay compatible) but we do not plan to support that specific release
> > > > > > over the long run.
> > > > > >
> > > > > > Florian
> > > > >
> > > > > Thank you very much!
> > > > > Tamas
> > > > >
> > > > > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > > > > júl. 17., H, 11:46):
> > > > > >
> > > > > > On Mon, 2023-07-17 at 11:36 +0200, Tamás Paál wrote:
> > > > > > > > Dear All,
> > > > > > > >
> > > > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > > > run into a kernel compilation error very early:
> > > > > > > >
> > > > > > > >
> > > > > > > > In file included from ./include/asm-generic/xenomai/ Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > > > "missing release" in our community call some days ago. There are some
> > > > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > > > >
> > > > > > > > Florian
> > > > > > >
> > > > > > > Thank you!
> > > > > > > Which kernel do you recommend to start working with. 6.1, or 6.4? Is
> > > > > > > the current master in a "working shape", or should I wait for a
> > > > > > > release?
> > > > > >
> > > > > > 6.1 is a LTS (Long Term Support) release, so it will stay for some
> > > > > > time, Xenomai support included.
> > > > > >
> > > > > > 6.4 is just a normal release and will vanish once 6.5. is out. We're
> > > > > > testing that in combination with latest Xenomai already (to make sure
> > > > > > we stay compatible) but we do not plan to support that specific release
> > > > > > over the long run.
> > > > > >
> > > > > > Florian
> > > > > >
> > > > > > >
> > > > > > > Thank you very much!
> > > > > > > Tamas
> > > > > > >
> > > > > > > Florian Bezdeka <florian.bezdeka@siemens.com> ezt írta (időpont: 2023.
> > > > > > > júl. 17., H, 11:15):
> > > > > > > >
> > > > > > > > On Mon, 2023-07-17 at 11:05 +0200, Tamás Paál wrote:
> > > > > > > > > Dear All,
> > > > > > > > >
> > > > > > > > > I am using the 5.15 dovetail based kernel together with Xenomai 3.2.1.
> > > > > > > > > It works fine. I would like to upgrade to a more recent kernel, but I
> > > > > > > > > run into a kernel compilation error very early:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > In file included from ./include/asm-generic/xenomai/syscall.h:26,
> > > > > > > > >                  from
> > > > > > > > > ./arch/x86/xenomai/dovetail/include/asm/xenomai/syscall.h:24,
> > > > > > > > >                  from ./include/xenomai/pipeline/pipeline.h:12,
> > > > > > > > >                  from ./include/xenomai/cobalt/kernel/lock.h:26,
> > > > > > > > >                  from ./include/xenomai/cobalt/kernel/sched.h:23,
> > > > > > > > >                  from ./arch/x86/include/dovetail/irq.h:12,
> > > > > > > > >                  from kernel/irq/pipeline.c:17:
> > > > > > > > > ./arch/x86/xenomai/include/asm/xenomai/wrappers.h:44:10: fatal error:
> > > > > > > > > asm/fpu/internal.h: No such file or directory
> > > > > > > > >    44 | #include <asm/fpu/internal.h>
> > > > > > > > >       |          ^~~~~~~~~~~~~~~~~~~~
> > > > > > > > > compilation terminated.
> > > > > > > > > make[3]: *** [scripts/Makefile.build:252: kernel/irq/pipeline.o] Error 1
> > > > > > > > > make[2]: *** [scripts/Makefile.build:494: kernel/irq] Error 2
> > > > > > > > > make[1]: *** [scripts/Makefile.build:494: kernel] Error 2
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I have been tried kernel 5.19, 6.1, 6.4, Xenomai 3.2.1, 3.2.3 in all
> > > > > > > > > combinations, with the same result.
> > > > > > > > > In kernel version 5.15 the arch/x86/include/asm/fpu directory contains
> > > > > > > > > an internal.h, but I cannot find this file from 5.19 and above. I
> > > > > > > > > believe this is the cause of the error.
> > > > > > > > >
> > > > > > > > > Please help me. What am I doing wrong?
> > > > > > > >
> > > > > > > > Xenomai 3.2.x supports Linux up to 5.15. If you want to update to newer
> > > > > > > > Linux versions you have to use Xenomai from master branch. There is no
> > > > > > > > 3.3 release yet, but we're working on it. We already discussed that
> > > > > > > > "missing release" in our community call some days ago. There are some
> > > > > > > > features pending that we would like to integrate. So: stay tuned.
> > > > > > > >
> > > > > > > > Florian
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Thank you,
> > > > > > > > > Tamas
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > >
> > >
> >
>