* (no subject)
@ 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
0 siblings, 2 replies; 3+ messages in thread
From: Michèl Alexandre Salim @ 2001-06-11 15:01 UTC (permalink / raw)
To: linux-kernel
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?
Regards,
Michel
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Clock drift on TransmetaCrusoe
2001-06-11 15:01 Michèl Alexandre Salim
@ 2001-06-11 18:20 ` george anzinger
2001-06-12 4:24 ` george anzinger
1 sibling, 0 replies; 3+ messages in thread
From: george anzinger @ 2001-06-11 18:20 UTC (permalink / raw)
To: Michèl Alexandre Salim; +Cc: linux-kernel
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, you best bet would be to use the xntpd code to sync to
another system.
George
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Clock drift on TransmetaCrusoe
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
1 sibling, 0 replies; 3+ messages in thread
From: george anzinger @ 2001-06-12 4:24 UTC (permalink / raw)
To: Michèl Alexandre Salim; +Cc: linux-kernel
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-06-12 23:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).