Hi all,
first issue:
maybe someone can explain what's going on here. I'm running autotune
inside qemu (ARM) on an x86_64 host and get the error below. The
kernel in use is 4.19 (ipipe) build with current "next" branch.
root@demo:~# autotune2
== auto-tuning started, period=1000000 ns (may take a while)
irq gravity... 0 ns
kernel gravity... autotune: tuning failed (kernel): Resource temporarily
unavailable
dmesg tells me
[ 92.800781] [Xenomai] autotune(irqhand) started
[ 102.499494] [Xenomai] autotune(kthread) started
[ 108.623898] [Xenomai] autotune(kthread) failed with early shot (827251 ns)
[ 108.646795] [Xenomai] autotune finished [0i/5000k/5000u]
Any idea why / how this early shot can happen? I'm unable to
reproduce it on a real hardware like the beagle bone black.
I wonder why it seems to work in the CI setup...
Second issue: From time to time autotune produces a segfault:
root@demo:~# autotune
== auto-tuning started, period=1000000 ns (may take a while)
irq gravity... 1984 ns
kernel gravity... 10912ns
user gravity... Segmentation fault
I haven't seen the segfault with a dovetail enabled kernel yet.
So it might be ipipe related...
I was able to reproduce once with gdb attached. We seem to crash
in rtmd.c line 170 (do_ioctl, XENOMAI_SYSCALL3()). GDB was
unable to present a backtrace. ("previous frame identical to this
frame (corrupt stack?")
TIA,
Florian
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
