mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: Clock incorrect on 2.6.31-rc2
Date: Thu, 9 Jul 2009 14:58:37 -0700	[thread overview]
Message-ID: <1f1b08da0907091458r19ff62c6md4436c86baf9254d@mail.gmail.com> (raw)
In-Reply-To: <20090709141000.584d199a@nehalam>

On Thu, Jul 9, 2009 at 2:10 PM, Stephen Hemminger<shemminger@vyatta.com> wrote:
> My system (desktop Ubuntu 9.0) runs fine with 2.6.30, but with 2.6.31-rc2 it does
> not keep time correctly. Also ntptime reports an error.

Can you better describe how it does not keep time? Is time moving too
slow? too fast?

Could you include output from the following commands with 2.6.31-rc2
(and 2.6.30 if you have the time).
 $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
 $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
 $ dmesg
 $ ntpdc -c peers
 $ ntpdc -c kerninfo

> $ ntptime
> ntp_gettime() returns code 5 (ERROR)
>  time ce00daf1.8e997000  Thu, Jul  9 2009 14:09:05.557, (.557029),
>  maximum error 25016 us, estimated error 16 us
> ntp_adjtime() returns code 5 (ERROR)
>  modes 0x0 (),
>  offset 0.000 us, frequency 7.827 ppm, interval 1 s,
>  maximum error 25016 us, estimated error 16 us,
>  status 0x40 (UNSYNC),
>  time constant 4, precision 1.000 us, tolerance 500 ppm,

The error above just comes from NTP not being in sync.

thanks
-john

  parent reply	other threads:[~2009-07-09 21:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 21:10 Stephen Hemminger
2009-07-09 21:45 ` Thomas Gleixner
2009-07-09 21:58 ` john stultz [this message]
2009-07-09 22:38   ` Stephen Hemminger
2009-07-09 23:22     ` john stultz
2009-07-09 23:30       ` Stephen Hemminger
2009-07-14 18:35         ` Philippe Troin
2009-07-15 22:57           ` john stultz
2009-09-11  3:29             ` Philippe Troin
2009-07-15 22:58         ` john stultz
2009-07-16 15:08           ` Stephen Hemminger

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=1f1b08da0907091458r19ff62c6md4436c86baf9254d@mail.gmail.com \
    --to=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=tglx@linutronix.de \
    /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®