Re: [Xenomai] CLOCK_HOST_REALTIME failure on Xenomai 3

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2015-04-16 18:12, GP Orcullo wrote:
> On Thu, Apr 16, 2015 at 9:43 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> On 2015-04-16 15:23, Gilles Chanteperdrix wrote:
>>> On Thu, Apr 16, 2015 at 07:20:09PM +0800, GP Orcullo wrote:
>>>> Hi,
>>>>
>>>> I'm trying to run Xenomai 3 on my Cubieboard2 but it fails the clocktest:
>>>>
>>>> # /usr/xenomai/bin/clocktest -C 42
>>>> clock_gettime failed for clock id == Tested clock: 42 (<unknown>)
>>>> CPU      ToD offset [us] ToD drift [us/s]      warps max delta [us]
>>>> --- -------------------- ---------------- ---------- --------------42
>>>>
>>>>   0                  0.0            0.000          0            0.0
>>>>   1                  0.0            0.000          0            0.0
>>>> clock_gettime failed for clock id 42
>>>>
>>>> The clock test runs fine on Xenomai 2:
>>>>
>>>> # clocktest -C 42
>>>> == Tested clock: 42 (CLOCK_HOST_REALTIME)
>>>> CPU      ToD offset [us] ToD drift [us/s]      warps max delta [us]
>>>> --- -------------------- ---------------- ---------- --------------
>>>>   0                  1.0            0.093          0            0.0
>>>>   1                  0.8            0.000          0            0.0
>>>> ^C
>>>
>>> CLOCK_HOST_REALTIME is no longer 42 in Xenomai 3 (which is why
>>> clocktest tells you that the clockid 42 is unknown, it really is).
>>>
>>
>> CLOCK_HOST_REALTIME is an extension clock, thus you need
>>
>> clocktest -E -C 42
>>
>> in Xenomai 3.
>>
>> Jan
>>
>> --
>> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
>> Corporate Competence Center Embedded Linux
> 
> The answer is 32 :)

Hehe, I missed some patches since then.

> 
> # /usr/xenomai/bin/clocktest -D -C 32
> hostrt data area is live
> sequence counter : 261312
> wall_time_sec    : 3698
> wall_time_nsec   : 660000622
> wall_to_monotonic_sec    : -2392
> wall_to_monotonic_nsec   : 103430917
> cycle_last       : 31565440899
> mask             : 0xffffffffffffffff
> mult             : 699050667
> shift            : 24
> 
> == Tested clock: 32 (CLOCK_HOST_REALTIME)
> CPU      ToD offset [us] ToD drift [us/s]      warps max delta [us]
> --- -------------------- ---------------- ---------- --------------
>   0                  1.4           -0.034          0            0.0
>   1                  1.4            0.134          0            0.0
> 
> 
> BTW, any idea on how to diagnose the switchtest issue? The test is
> running but it is not generating any output. It looks like "-q -Q"
> switches are enabled.

ftrace (trace-cmd)? You would see what the core does while switchtest is
active without disturbing switchtest via gdb.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux