From: Juergen Beisert <jbe@pengutronix.de>
To: linux-kernel@vger.kernel.org
Subject: CMOS time jumps when ntpd ist running
Date: Tue, 11 Aug 2009 10:00:00 +0200 [thread overview]
Message-ID: <200908111000.01316.jbe@pengutronix.de> (raw)
Hi list,
anybody here who saw such CMOS clock behaviour when ntpd is running?
I synced system and CMOS time and after that I ran a simple
'watch -t -n 300 "date; hwclock -u" > /logfile'
(note: When the ntpd daemon is not running, the CMOS clock does not show this
behaviour):
[...]
Mon Aug 10 03:53:20 CEST 2009 <-- system time
Mon Aug 10 03:53:20 2009 0.000000 seconds <-- CMOS time
Mon Aug 10 03:58:20 CEST 2009
Mon Aug 10 03:58:20 2009 0.000000 seconds
Mon Aug 10 04:03:20 CEST 2009
Sun Aug 9 22:03:20 2009 0.000000 seconds <----- BANG !!!!!!111!1!!
Mon Aug 10 04:08:20 CEST 2009
Sun Aug 9 22:08:20 2009 0.000000 seconds
[...]
It seems its always -6 hours the CMOS clock jumps. And sometimes -(6h + n *
24h) with n from 1 to 3 I saw.
Is my CMOS clock broken? (BTW: x86 arch, 32 bit, Linux kernel 2.6.28.10 and
there is no SMM code in the system, it runs coreboot)
Regards
Juergen
reply other threads:[~2009-08-11 12:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200908111000.01316.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®