Re: [Xenomai-help] Hang at glibc time() function call

["Petr Cervenka" <grugh@domain.hid>]

>Could not it be that the highest priority task is using all the CPU?

No, it's highly unprobable. The task runs at is should.

>Is the low priority task also mapped as Xenomai task? In that case
>calling standard Linux time services can be lethal:

Yes, the task is mapped as Xenomai task, because it waits on real-time queue with some timeout.

>
>If the Linux clocksource is TSC or HPET, glibc will use a syscall-less
>variant for time of day reading. That variant has two properties:
>
>A) It doesn't switch Xenomai task into secondary mode like ordinary
>   syscalls do.
>
>B) It can deadlock with the Linux kernel, leaving the caller spinning
>   forever so that Linux is no longer executed.

Hmm, probably my cause.

Meanwhile I replaced the glibc time() function call with rt_timer_read and it seems to work fine now (for 3 days).

Thank you for you support.
Petr