[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200806041622.49593.lkm@lea-linux.com>
Date: Wed, 4 Jun 2008 16:22:49 +0200
From: Lkm <lkm@...-linux.com>
To: "Bart Van Assche" <bart.vanassche@...il.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: PROBLEM: Hardware clock instable
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@...-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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists