Hello
we are using the xenomai-forge implementation.
We from time to time see an issue that the timer-internal thread is
consuming a complete core. It is seen when we send broadcast traffic that
needs to be handled by the Linux kernel (ARP).
The kernel thread's priority handling the packets in th
> Well, then you need to replace #ifdef CONFIG_PREEMPT_RT with
> CONFIG_PREEMPT_RT_FULL, and test the kernel version in wrappers.h to
> define CONFIG_PREEMPT_RT_FULL if CONFIG_PREEMPT_RT is dedined for
> old kernels.
I have applied both changes and try if this solves the my problem. If it works
On Sun, Dec 07, 2014 at 01:50:02PM +, Stoidner, Christoph wrote:
>
>
> > From what I understand of Xenomai 2.6 code (if this is the version
> > you are using),
>
> Yes, I am using Xenomai 2.6
>
> > normally, the apc should be invoked from the
> > rthal_apc_thread context, not from rthal_ap
> From what I understand of Xenomai 2.6 code (if this is the version
> you are using),
Yes, I am using Xenomai 2.6
> normally, the apc should be invoked from the
> rthal_apc_thread context, not from rthal_apc_handler.
>
> The virq handler should be rthal_apc_kicker, which wakes up the
> proces
On Sat, Dec 06, 2014 at 02:19:27PM +, Stoidner, Christoph wrote:
>
> Hi at all,
>
> I am using linux 3.10.18 and ipipe-core-3.10.18-arm-1 on a Freescale i.MX28.
> I have also merged PREEMPT RT rt14 into the kernel. FCSE is disabled.
>
> I have enabled several debug options in the kernel. Wh
>> If you have lockdep enabled, you should disable it, as it currently
>> does not work with xenomai on arm.
> lockdep is disabled in my kernel config.
>From my understanding the output
[ 33.187125] in_atomic(): 1, irqs_disabled(): 128, pid: 87, name:
[ 33.187138] 1 lock held by /87:
tel
