Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Oct 2000 14:02:50 +0200
From:      Alain Thivillon <Alain.Thivillon@hsc.fr>
To:        current@freebsd.org
Subject:   -CURRENT clock deviation
Message-ID:  <20001004140250.H5060@yoko.hsc.fr>

next in thread | raw e-mail | index | archive | help

I have noticed that -CURRENT (build last week) is subject to a very high
clock deviation:

Oct  4 12:14:08 yoko ntpd[674]: time reset 1.367273 s
Oct  4 12:14:08 yoko ntpd[674]: synchronisation lost
Oct  4 12:32:26 yoko ntpd[674]: synchronisation lost
Oct  4 12:41:06 yoko ntpd[674]: time reset 4.372092 s
Oct  4 12:41:06 yoko ntpd[674]: synchronisation lost
Oct  4 13:01:31 yoko ntpd[674]: time reset 1.410883 s
Oct  4 13:01:31 yoko ntpd[674]: synchronisation lost
Oct  4 13:23:06 yoko ntpd[674]: time reset 3.039882 s
Oct  4 13:23:06 yoko ntpd[674]: synchronisation lost

My ntp server is not the cause, other clients have no problems.

Deviation seems to be around 5 seconds / 30 min.

I run -CURRENT on a laptop, it seems that last commit in idle loop (the
one replacing loop by HLT and lowering temperature) broke the clock.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001004140250.H5060>