From owner-freebsd-stable@FreeBSD.ORG Fri Feb 12 12:26:09 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C7061065679 for ; Fri, 12 Feb 2010 12:26:09 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.freebsd.org (Postfix) with ESMTP id 191ED8FC15 for ; Fri, 12 Feb 2010 12:26:08 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0KXQ00FO7AJ1QH30@bgo1smout1.broadpark.no> for freebsd-stable@freebsd.org; Fri, 12 Feb 2010 13:25:49 +0100 (CET) Received: from kg-v2.kg4.no ([80.203.92.186]) by bgo1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0KXQ00LEPAJ0TDW0@bgo1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Fri, 12 Feb 2010 13:25:49 +0100 (CET) Date: Fri, 12 Feb 2010 13:25:48 +0100 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20100212132548.8aed4d16.torfinn.ingolfsen@broadpark.no> In-reply-to: References: <20100211190652.6a66c618.torfinn.ingolfsen@broadpark.no> X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.6; amd64-portbld-freebsd8.0) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: ntpd struggling to keep up - how to fix? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2010 12:26:09 -0000 On Thu, 11 Feb 2010 10:25:59 -0800 Chuck Swiger wrote: > The rate at which this machine is losing time is probably exceeding the ~50 seconds per day that NTPd is willing to correct without extreme measures (ie, it has to step time rather than drift-correct). > You might help it maintain a more sane idea of time by using at least 4 timeservers. Hmm, ok that iis something I can try. > You might take a look at 'vmstat -i' and look out for an interrupt storm, but it's possible your hardware's clock is simply busted. AFAICT, vmstat -i looks ok: root@kg-f2# uptime 1:23PM up 18:31, 3 users, load averages: 0.00, 0.00, 0.00 root@kg-f2# vmstat -i interrupt total rate irq1: atkbd0 36 0 irq6: fdc0 1 0 irq16: siis0 ohci0+ 408 0 irq22: atapci0 856338 12 cpu0: timer 133347678 1999 irq256: re0 234087 3 cpu1: timer 133337654 1999 Total 267776202 4016 -- Regards, Torfinn