From owner-freebsd-current Wed Oct 4 5: 2:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id E678337B503 for ; Wed, 4 Oct 2000 05:02:54 -0700 (PDT) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "yoko.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id E1B1A10E04 for ; Wed, 4 Oct 2000 14:02:53 +0200 (CEST) Received: by yoko.hsc.fr (Postfix-TLS, from userid 1001) id 4022A9B387; Wed, 4 Oct 2000 14:02:50 +0200 (CEST) Date: Wed, 4 Oct 2000 14:02:50 +0200 From: Alain Thivillon To: current@freebsd.org Subject: -CURRENT clock deviation Message-ID: <20001004140250.H5060@yoko.hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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