From: Lkm <lkm@lea-linux.com>
To: "Bart Van Assche" <bart.vanassche@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Hardware clock instable
Date: Wed, 4 Jun 2008 15:17:43 +0200 [thread overview]
Message-ID: <200806041517.43347.lkm@lea-linux.com> (raw)
In-Reply-To: <e2e108260806040549p11117410x192d1020adb885c7@mail.gmail.com>
Le Wednesday 04 June 2008 14:49:58 Bart Van Assche, vous avez écrit :
> On Wed, Jun 4, 2008 at 2:02 PM, Lkm <lkm@lea-linux.com> wrote:
> > i work in a web hosting compagny. We have a strange problem on many
> > servers. The hardware clock of several server is totaly instable. This
> > happen on many server, not all.
>
> Which messages are logged by the NTP daemon during the first 24 hours
> after it has been started ? On Debian systems you can install NTP by
> running apt-get install ntp.
>
> Bart.
Ntpd logs:
28 May 10:32:17 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
28 May 10:51:34 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
29 May 00:20:57 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
29 May 01:46:28 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
29 May 02:27:10 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
29 May 02:33:34 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
29 May 02:39:02 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
29 May 04:02:28 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
29 May 04:45:12 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
29 May 09:01:20 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
31 May 16:16:55 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
31 May 17:33:50 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
31 May 17:59:26 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
31 May 18:33:32 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
31 May 18:47:22 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
31 May 18:52:04 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
31 May 18:55:53 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
31 May 19:49:25 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
31 May 20:28:30 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
31 May 21:45:19 ntpd[31086]: synchronized to 192.168.0.151, stratum 3
2 Jun 05:28:59 ntpd[31086]: synchronized to 192.168.0.150, stratum 3
2 Jun 10:46:26 ntpd[31086]: ntpd exiting on signal 15
2 Jun 10:53:32 ntpd[2299]: synchronized to 192.168.0.150, stratum 3
2 Jun 10:53:32 ntpd[2299]: kernel time sync enabled 0001
2 Jun 11:02:11 ntpd[2299]: synchronized to 192.168.0.151, stratum 3
2 Jun 11:06:36 ntpd[2299]: synchronized to 192.168.0.150, stratum 3
2 Jun 11:19:26 ntpd[2299]: synchronized to 192.168.0.151, stratum 3
2 Jun 11:55:56 ntpd[2299]: synchronized to 192.168.0.150, stratum 3
2 Jun 12:34:24 ntpd[2299]: synchronized to 192.168.0.151, stratum 3
2 Jun 13:00:08 ntpd[2299]: synchronized to 192.168.0.150, stratum 3
2 Jun 13:33:44 ntpd[2299]: ntpd exiting on signal 15
2 Jun 13:42:20 ntpd[2299]: synchronized to 192.168.0.150, stratum 3
2 Jun 13:42:20 ntpd[2299]: time reset -109.498922 s
2 Jun 13:42:20 ntpd[2299]: kernel time sync enabled 0001
2 Jun 13:45:34 ntpd[2299]: synchronized to 192.168.0.151, stratum 3
2 Jun 14:21:59 ntpd[2299]: synchronized to 192.168.0.150, stratum 3
2 Jun 14:30:41 ntpd[2299]: synchronized to 192.168.0.151, stratum 3
2 Jun 15:33:28 ntpd[2299]: ntpd exiting on signal 15
2 Jun 15:39:55 ntpd[2300]: ntpd exiting on signal 15
2 Jun 15:46:39 ntpd[2354]: synchronized to 192.168.0.150, stratum 3
2 Jun 15:46:39 ntpd[2354]: kernel time sync enabled 0001
2 Jun 15:54:11 ntpd[2354]: synchronized to 192.168.0.151, stratum 3
2 Jun 15:59:36 ntpd[2354]: synchronized to 192.168.0.150, stratum 3
2 Jun 16:27:25 ntpd[2354]: synchronized to 192.168.0.151, stratum 3
2 Jun 16:36:06 ntpd[2354]: synchronized to 192.168.0.150, stratum 3
2 Jun 17:01:40 ntpd[2354]: synchronized to 192.168.0.151, stratum 3
2 Jun 17:50:52 ntpd[2354]: synchronized to 192.168.0.150, stratum 3
3 Jun 01:31:52 ntpd[2354]: synchronized to 192.168.0.151, stratum 3
Other (useful?) logs:
Jun 4 14:29:53 rd10 kernel: set_rtc_mmss: can't update from 77 to 29
Jun 4 14:29:54 rd10 kernel: set_rtc_mmss: can't update from 77 to 29
Jun 4 14:29:55 rd10 kernel: set_rtc_mmss: can't update from 77 to 29
Jun 4 14:29:56 rd10 kernel: set_rtc_mmss: can't update from 77 to 29
Jun 4 14:29:57 rd10 kernel: set_rtc_mmss: can't update from 77 to 29
Jun 4 14:29:58 rd10 kernel: set_rtc_mmss: can't update from 77 to 29
Jun 4 14:29:59 rd10 kernel: set_rtc_mmss: can't update from 77 to 29
Jun 4 14:30:00 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:01 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:02 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:03 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:04 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:05 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:06 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:07 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:08 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:09 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:10 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:11 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:12 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:13 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:14 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:15 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:16 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:17 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:18 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:19 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:20 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:21 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:22 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:23 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:24 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:25 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:26 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:27 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:28 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:29 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:30 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:31 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:32 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:33 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:34 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:35 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:36 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:37 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:38 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:39 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:40 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:41 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:42 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:43 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:44 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:45 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:46 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
Jun 4 14:30:47 rd10 kernel: set_rtc_mmss: can't update from 78 to 30
:
next prev parent reply other threads:[~2008-06-04 13:19 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 [this message]
2008-06-04 13:40 ` Bart Van Assche
2008-06-04 14:22 ` Lkm
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=200806041517.43347.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.