I have a machine with a sempron64 and it seems that time is a tad bit too
fast. Every minute it skips ahead about 15-20 seconds. After about 10
minutes it's several minutes ahead of the real time. For now I've set a
cron job to rdate time.nist.gov every 5 minutes. This is on BSD 3.8
with the generic kernel and no other special modifications. Is there
anything I can possibly do to fix this little glitch (perhaps something
via sysctl?) or is it a problem in the code somewhere? Any help would be
greatly appreciated, thanks.
- Cyrus

are you running ntpd? are you running ntpd with the kernel adjtime
patch i posted to tech a few days ago?

1/1/06, Cyrus Lopez <cyrus (AT) cyruslabs (DOT) comwrote:
I have a machine with a sempron64 and it seems that time is a tad bit too
fast. Every minute it skips ahead about 15-20 seconds. After about 10
minutes it's several minutes ahead of the real time. For now I've set a
cron job to rdate time.nist.gov every 5 minutes. This is on BSD 3.8
with the generic kernel and no other special modifications. Is there
anything I can possibly do to fix this little glitch (perhaps something
via sysctl?) or is it a problem in the code somewhere? Any help would be
greatly appreciated, thanks.
--
- Cyrus

Tuesday 03 January 2006 15:16, Ted Unangst wrote:
are you running ntpd? are you running ntpd with the kernel adjtime
patch i posted to tech a few days ago?

1/1/06, Cyrus Lopez <cyrus (AT) cyruslabs (DOT) comwrote:
I have a machine with a sempron64 and it seems that time is a tad bit too
fast. Every minute it skips ahead about 15-20 seconds. After about 10
minutes it's several minutes ahead of the real time. For now I've set a
cron job to rdate time.nist.gov every 5 minutes. This is on BSD 3.8
with the generic kernel and no other special modifications. Is there
anything I can possibly do to fix this little glitch (perhaps something
via sysctl?) or is it a problem in the code somewhere? Any help would be
greatly appreciated, thanks.
--
- Cyrus

I missed your original post. What is the make/model of the computer. There
is a known issue on some machines with the clock running fast with AMD/ATI on
Linux. It *might* be the same with BSD.

Gateway MX7515m

AMD/ATI bug - clock runs at double speed

I used - noapictimer at boot on my Linux notebook to fix the issue.

Not sure that's going to help. But if it is a hardware issue, that may be
enough of a start for a developer to help.

Provide your hardware info.

RegardsMartin

Tue, 03 Jan 2006 14:16:17 -0600, Ted Unangst <ted.unangst (AT) gmail (DOT) com
wrote:

are you running ntpd? are you running ntpd with the kernel adjtime
patch i posted to tech a few days ago?

1/1/06, Cyrus Lopez <cyrus (AT) cyruslabs (DOT) comwrote:
>I have a machine with a sempron64 and it seems that time is a tad bit
>too
>fast. Every minute it skips ahead about 15-20 seconds. After about 10
>minutes it's several minutes ahead of the real time. For now I've set a
>cron job to rdate time.nist.gov every 5 minutes. This is on BSD 3.8
>with the generic kernel and no other special modifications. Is there
>anything I can possibly do to fix this little glitch (perhaps something
>via sysctl?) or is it a problem in the code somewhere? Any help would be
>greatly appreciated, thanks.
>>
>>
>- Cyrus
>>
>>

Actually I just started running NTPD and now the time is in sync with the
real time. Although I do notice that ntpd adjusts the time quite a bit via
the logs. However, that matters not to me as long as the server has fairly
accurate time which it does now. Thanks for all the prompt replies.
- Cyrus