From owner-freebsd-current@FreeBSD.ORG Sat Aug 23 22:45:11 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 904941065671 for ; Sat, 23 Aug 2008 22:45:11 +0000 (UTC) (envelope-from rmtodd@ichotolot.servalan.com) Received: from mx1.synetsystems.com (mx1.synetsystems.com [76.10.206.14]) by mx1.freebsd.org (Postfix) with ESMTP id 6FE0C8FC19 for ; Sat, 23 Aug 2008 22:45:11 +0000 (UTC) (envelope-from rmtodd@ichotolot.servalan.com) Received: by mx1.synetsystems.com (Postfix, from userid 66) id C7F36C3D; Sat, 23 Aug 2008 18:45:10 -0400 (EDT) Received: from localhost ([127.0.0.1]:60339 helo=ichotolot.servalan.com) by servalan.servalan.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1KX1Mj-000AdK-9q for freebsd-current@freebsd.org; Sat, 23 Aug 2008 17:13:49 -0500 To: freebsd-current@freebsd.org Date: Sat, 23 Aug 2008 17:13:49 -0500 From: Richard Todd Message-Id: <20080823224510.C7F36C3D@mx1.synetsystems.com> Subject: Weirdness with recently updated NTP on -current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2008 22:45:11 -0000 I just today updated my system to the most recent -current. Upon rebooting, I noticed that NTP seemed to be seriously confused: Aug 23 16:29:01 ichotolot ntpd[1694]: time correction of -433225776 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. Further experimentation revealed that indeed, the newly updated NTP seems to be somewhat confused. Behold the following transcript. Note that "ntpdate" is the -current ntpdate in /usr/sbin, and /snap/usr:daily.200808230000/sbin/ntpdate is the ntpdate from my previous -current build as of last July. The old ntpdate gives a sane value for the time offset between my machine and another one on the local LAN, but the new ntpdate gives something totally out-of-whack: Script started on Sat Aug 23 17:05:42 2008 ichotolot# ntpdate -q -v -v aagenfelt 23 Aug 17:06:18 ntpdate[24205]: ntpdate 4.2.4p5-a Sat Aug 23 15:03:37 CDT 2008 (1) server 10.0.0.8, stratum 3, offset -866449315.927817, delay 0.02515 23 Aug 17:06:18 ntpdate[24205]: step time server 10.0.0.8 offset -866449315.927817 sec ichotolot# /snap/usr:daily.200808230000/sbin/ntpdate -q -v -v aagenfelt 23 Aug 17:06:33 ntpdate[25545]: ntpdate 4.2.0-a Tue Jul 29 19:06:12 CDT 2008 (1) server 10.0.0.8, stratum 3, offset 1.102235, delay 0.02666 23 Aug 17:06:33 ntpdate[25545]: step time server 10.0.0.8 offset 1.102235 sec ichotolot# exit Script done on Sat Aug 23 17:06:41 2008 (Also note that the out-of-whack value from ntpdate doesn't match the out-of-whack value from ntpd either.) Has anyone else seen anything like this? This is on a Core2Duo system running FreeBSD in i386 mode.