From: Thomas Lockhart <Thomas.Lockhart@domain.hid>
To: Josh Karch <JKarch@domain.hid>, Steve Deiters <SteveDeiters@domain.hid>
Cc: Jan Kiszka <jan.kiszka@domain.hid>,
Andreas Glatz <AndreasGlatz@domain.hid>,
"Mauerer, Wolfgang" <wolfgang.mauerer@domain.hid>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Question about getting system time
Date: Mon, 17 May 2010 11:51:40 -0700 [thread overview]
Message-ID: <4BF1903C.50801@domain.hid> (raw)
In-Reply-To: <843773D242212C4882D4EDFFBF665F7F0C9F71BAFF@FW-SBS.fw.local>
> If no ntp server updates are made to the Linux clock, we have
> noticed over a week's period a drift of ten or so seconds difference
> between the Linux clock and the Xenomai get time function and often
> have to reboot our machine to resynchronize the Xenomai and Linux
> clocks back to less than a couple seconds difference. I was
> wondering if you might explain why that might happen?
Your clock oscillator on the x86 PC is drifting wrt NTP time (the
oscillators are known to be bad time sources). We see the same effect
here. With NTP running, try running a RT periodic thread and obtain both
Linux system time and Xenomai RT time. You will see a sawtooth time
difference reaching around 1msec in magnitude before NTP readjusts Linux
system time back down to near zero. Then the clocks drift wrt one
another until you have around a 1msec difference, and NTP adjusts the
time again. I recall a periodicity of around 30-60sec per adjustment
cycle (5-10 seconds per week) but it is dependent on the characteristics
of your specific oscillator on the motherboard.
I have thought to cope with this by having a rate parameter on the code
encapsulating my timing source (I have "drivers" for Linux system time,
Xenomai time, and hardware timing sources). The NTP rate in the drift
file is pretty constant, so one could presumably use that rate to adjust
your timers.
hth
- Tom
next prev parent reply other threads:[~2010-05-17 18:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 22:14 [Xenomai-help] Question about getting system time Abhijit Majumdar
2010-05-14 5:44 ` Gilles Chanteperdrix
2010-05-14 10:34 ` Andreas Glatz
2010-05-14 10:42 ` Gilles Chanteperdrix
2010-05-17 16:27 ` Steve Deiters
2010-05-17 16:52 ` Jan Kiszka
2010-05-17 17:05 ` Steve Deiters
2010-05-17 17:13 ` Jan Kiszka
2010-05-17 18:02 ` Josh Karch
2010-05-17 18:23 ` Jan Kiszka
2010-05-17 18:51 ` Thomas Lockhart [this message]
2010-05-17 22:48 ` Steve Deiters
2010-05-17 23:50 ` Gilles Chanteperdrix
2010-05-17 23:53 ` Gilles Chanteperdrix
2010-05-18 0:23 ` Steve Deiters
2010-05-18 7:04 ` Jan Kiszka
2010-05-18 7:59 ` Gilles Chanteperdrix
2010-05-18 8:38 ` Wolfgang Mauerer
2010-05-18 10:11 ` Gilles Chanteperdrix
2010-05-18 12:11 ` Wolfgang Mauerer
2010-05-18 12:41 ` Gilles Chanteperdrix
2010-05-18 14:58 ` [Xenomai-core] " Wolfgang Mauerer
2010-05-18 15:07 ` Gilles Chanteperdrix
2010-05-18 18:41 ` Gilles Chanteperdrix
2010-05-18 20:23 ` Wolfgang Mauerer
2010-05-18 21:19 ` Gilles Chanteperdrix
2010-05-18 22:09 ` Jan Kiszka
2010-05-18 22:24 ` Gilles Chanteperdrix
2010-05-18 23:02 ` Jan Kiszka
2010-05-19 5:49 ` Gilles Chanteperdrix
2010-05-19 7:11 ` Jan Kiszka
2010-05-21 8:55 ` Gilles Chanteperdrix
2010-05-27 15:35 ` Wolfgang Mauerer
2010-05-19 19:16 ` Daniele Nicolodi
2010-05-19 20:55 ` Gilles Chanteperdrix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF1903C.50801@domain.hid \
--to=thomas.lockhart@domain.hid \
--cc=AndreasGlatz@domain.hid \
--cc=JKarch@domain.hid \
--cc=SteveDeiters@domain.hid \
--cc=jan.kiszka@domain.hid \
--cc=wolfgang.mauerer@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.