mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Perkel <mperkel@yahoo.com>
To: Bart Van Assche <bart.vanassche@gmail.com>,
	Chris Snook <csnook@redhat.com>
Cc: Marc Perkel <mperkel@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: AMD Quad Core clock problem?
Date: Wed, 16 Apr 2008 14:44:56 -0700 (PDT)	[thread overview]
Message-ID: <414144.49021.qm@web52506.mail.re2.yahoo.com> (raw)
In-Reply-To: <e2e108260804142311r7ca31d29m7221ca8935a79f35@mail.gmail.com>


--- Bart Van Assche <bart.vanassche@gmail.com> wrote:

> On Mon, Apr 14, 2008 at 9:16 PM, Chris Snook
> <csnook@redhat.com> wrote:
> > Marc Perkel wrote:
> >
> > > My best guess at this time is that the drift of
> this
> > > computer using the quad core is so great that
> the ntpd
> > > can't get in sync. Is there any way to make ntpd
> more
> > > agressive by setting something in ntp.conf?
> > >
> >
> >  ntp can correct for 500 ppm drift, which equates
> to 1.8 seconds per hour.
> > Beyond that you need to run ntpdate or ntpd -gq
> from cron to correct it.
> 
> It's better to correct the clock frequency once with
> the tickadj or
> adjtimex, so you don't have to add ntpdate to cron
> and you can still
> run ntpd.
> 
> Bart.
> 

ok - thanks. How do I do that?


Marc Perkel
Junk Email Filter dot com
http://www.junkemailfilter.com


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

  reply	other threads:[~2008-04-16 21:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 18:27 Marc Perkel
2008-04-11 18:35 ` H. Willstrand
2008-04-11 18:38 ` Chris Snook
2008-04-11 20:28   ` Marc Perkel
2008-04-11 21:11     ` Chris Snook
2008-04-11 21:36       ` Marc Perkel
2008-04-11 21:38         ` Lennart Sorensen
2008-04-13 19:35           ` H. Peter Anvin
2008-04-14 15:12             ` Lennart Sorensen
2008-04-14 16:23               ` H. Peter Anvin
2008-04-14 16:29                 ` Lennart Sorensen
2008-04-15  1:11               ` Krzysztof Halasa
2008-04-15  1:24                 ` H. Peter Anvin
2008-04-15  1:45                   ` Krzysztof Halasa
2008-04-15  2:40                     ` H. Peter Anvin
2008-04-11 21:46         ` Krzysztof Halasa
2008-04-11 22:09       ` Marc Perkel
2008-04-13  8:19         ` Bart Van Assche
2008-04-12  1:04       ` Marc Perkel
2008-04-14 19:16         ` Chris Snook
2008-04-14 20:46           ` Marc Perkel
2008-04-15  6:11           ` Bart Van Assche
2008-04-16 21:44             ` Marc Perkel [this message]
2008-04-17  6:17               ` Bart Van Assche
2008-04-17 18:03                 ` Marc Perkel
2008-04-18 11:56                   ` Bart Van Assche
2008-06-17 21:09           ` Marc Perkel
2008-04-14 13:40       ` Marc Perkel

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=414144.49021.qm@web52506.mail.re2.yahoo.com \
    --to=mperkel@yahoo.com \
    --cc=bart.vanassche@gmail.com \
    --cc=csnook@redhat.com \
    --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®