From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 03:08:45 2010 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 C2B40106564A for ; Mon, 6 Dec 2010 03:08:45 +0000 (UTC) (envelope-from james-freebsd-current@jrv.org) Received: from mail.jrv.org (adsl-70-243-84-13.dsl.austtx.swbell.net [70.243.84.13]) by mx1.freebsd.org (Postfix) with ESMTP id 573DB8FC13 for ; Mon, 6 Dec 2010 03:08:45 +0000 (UTC) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.14.3) with ESMTP id oB62UBUU069487 for ; Sun, 5 Dec 2010 20:30:11 -0600 (CST) (envelope-from james-freebsd-current@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-current@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: content-type:content-transfer-encoding; b=LKKxmGyfRObozfvC7jjxJeJZrRXm0da4Z8u9tkh/5fDo3k8pRTQ6Tzz7TvlOUaJ2n sXs7JNObN+/CSUP4RTGbgl48RC8Dr/XC1OQhnwhCHrXzSsTwcbpmvN37QqNiDyoMZnA f/HJ3Xsp30k9lPHtIN/uCwx7rmpRzXnEQLH83uU= Message-ID: <4CFC4AB3.4090604@jrv.org> Date: Sun, 05 Dec 2010 20:30:11 -0600 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: ts_to_ct messages; ntp: time correction of -1200 seconds exceeds sanity limit 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: Mon, 06 Dec 2010 03:08:45 -0000 FreeBSD gohorns.x 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r216088: Thu Dec 2 23:20:14 CST 2010 root@gohorns.x:/usr/obj/usr/src/sys/GENERIC amd64 I have been getting a lot of ts_to_ct for months: are we supposed to look for something or report anything about these? I just noticed an NTP error in /var/log/messages: ... Dec 4 02:52:18 gohorns kernel: ts_to_ct(1291431138.717914676) = [2010-12-04 02:52:18] Dec 4 03:09:05 gohorns ntpd[1934]: time reset +2.018106 s Dec 4 03:09:05 gohorns kernel: ts_to_ct(1291432145.779273676) = [2010-12-04 03:09:05] Dec 4 03:11:40 gohorns kernel: ts_to_ct(1291432301.024288164) = [2010-12-04 03:11:41] Dec 4 03:45:36 gohorns ntpd[1934]: time reset +1.976613 s Dec 4 03:45:36 gohorns kernel: ts_to_ct(1291434336.662385061) = [2010-12-04 03:45:36] Dec 4 03:45:36 gohorns ntpd[1934]: kernel time sync status change 6001 Dec 4 03:45:36 gohorns kernel: ts_to_ct(1291434336.712917848) = [2010-12-04 03:45:36] Dec 4 03:46:38 gohorns ntpd[1934]: time correction of -1200 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. Dec 4 04:15:36 gohorns kernel: ts_to_ct(1291436136.712892982) = [2010-12-04 04:15:36] Dec 4 04:45:36 gohorns kernel: ts_to_ct(1291437936.712891437) = [2010-12-04 04:45:36] Dec 4 05:15:36 gohorns kernel: ts_to_ct(1291439736.712890731) = [2010-12-04 05:15:36] ... At "Sun Dec 5 19:56:19 CST 2010" according to other systems, this machine says the time is gohorns:/root# date Sun Dec 5 20:11:01 CST 2010 gohorns:/root# Has anyone seen anything like this? Suggestions on what to look for as a cause? The system is a Dell Zino HD, dmesg: CPU: AMD Athlon(tm) Neo X2 Dual Core Processor 6850e (1800.10-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60fb2 Family = f Model = 6b Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f TSC: P-state invariant