From: george anzinger <george@mvista.com>
To: "Michèl Alexandre Salim" <salimma1@yahoo.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Clock drift on TransmetaCrusoe
Date: Mon, 11 Jun 2001 21:24:02 -0700 [thread overview]
Message-ID: <3B259962.88C35F88@mvista.com> (raw)
In-Reply-To: <20010611150111.7747.qmail@web3505.mail.yahoo.com>
Michèl Alexandre Salim wrote:
>
> Hello,
>
> Searching through the mailing list I could not find a
> reference to this problem, hence this post.
>
> Having ran various kernel and distribution
> combinations (SGI's 2.4.2-xfs bundled with their Red
> Hat installer, 2.4-xfs-1.0 and 2.4 CVS trees, Linux
> Mandrake with default kernel 2.4.3, and lastly
> 2.4.5-ac9), compiled for generic i386 and/or Transmeta
> Crusoe with APM off or on, one thing sticks out : a
> clock drift of a few minutes per day.
>
> This problem might not be noticeable for most users
> since notebooks are not normally left running that
> long, but it is rather serious. I can choose not to
> sync the software and hardware clock on shutdown and
> re-read the hardware clock every hour or so but it is
> rather kludgy.
>
> Anyone experienced this before or willing to try it
> out?
>
This is most likely a bad "rock" (crystal) in the box. There is a
"built in" drift of about .1445 seconds a day (runs too slow) due to the
fact that 1.193180Mhz can not be divided to 10 ms. but you are way over
this.
Here is a bit of code to sync your system to the RTC:
http://www.linuxppc.org/software/index/linuxppc_stable/software/adjtimex-1.9-3.ppc.html
Of course, your best bet would be to use the xntpd code to sync to
another system.
George
P.S
Please excuse me if this is a repeat, but I never saw my first post on
the list.
G.
prev parent reply other threads:[~2001-06-12 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 15:01 Michèl Alexandre Salim
2001-06-11 18:20 ` Clock drift on TransmetaCrusoe george anzinger
2001-06-12 4:24 ` george anzinger [this message]
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=3B259962.88C35F88@mvista.com \
--to=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=salimma1@yahoo.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).