All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lkm <lkm@lea-linux.com>
To: "Bart Van Assche" <bart.vanassche@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Hardware clock instable
Date: Wed, 4 Jun 2008 16:22:49 +0200	[thread overview]
Message-ID: <200806041622.49593.lkm@lea-linux.com> (raw)
In-Reply-To: <e2e108260806040640k3ffb9712j443c2da37feb394c@mail.gmail.com>

Le Wednesday 04 June 2008 15:40:49 Bart Van AsscI de, vous avez écrit :
> On Wed, Jun 4, 2008 at 3:17 PM, Lkm <lkm@lea-linux.com> wrote:
> > Ntpd logs:
>
> ...
>
> >  2 Jun 13:42:20 ntpd[2299]: time reset -109.498922 s
>
> ...
>
> The reason I asked for the ntpd logs is that I'm still not sure
> whether there is a hardware problem.

In fact i'm wondering too .... But we have so many server with the same 
problem...

> How long was the ntpd process 
> running when the above line was logged ?

I have rebooted the server on Mon Jun  2 13:37 (show in last command) for 
testing clock and clocksource boot argument.
If i look forward in the log:
26 Feb 11:25:12 ntpd[2422]: time reset -0.492486 s
I Don't know if we have rebooted the server this day..


> And can you also post the 
> output of ntpq -pn ?
>
ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+192.168.0.150   195.220.194.193  3 u  531 1024  377    1.398    0.606   0.402
*192.168.0.151   194.2.0.28       3 u  399 1024  377    0.554    0.426   0.172

> Bart.



  reply	other threads:[~2008-06-04 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 12:02 PROBLEM: Hardware clock instable Lkm
2008-06-04 12:49 ` Bart Van Assche
2008-06-04 13:17   ` Lkm
2008-06-04 13:40     ` Bart Van Assche
2008-06-04 14:22       ` Lkm [this message]
2008-06-04 14:38         ` Bart Van Assche

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=200806041622.49593.lkm@lea-linux.com \
    --to=lkm@lea-linux.com \
    --cc=bart.vanassche@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.