From owner-freebsd-stable@FreeBSD.ORG Sat Feb 13 18:50:35 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 6A3FD10656A8 for ; Sat, 13 Feb 2010 18:50:35 +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 2302C8FC15 for ; Sat, 13 Feb 2010 18:50:34 +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 <0KXS002SJN09X970@bgo1smout1.broadpark.no> for freebsd-stable@freebsd.org; Sat, 13 Feb 2010 19:50:34 +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 <0KXS001VEN09WYF2@bgo1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Sat, 13 Feb 2010 19:50:33 +0100 (CET) Date: Sat, 13 Feb 2010 19:50:33 +0100 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20100213195033.f888420c.torfinn.ingolfsen@broadpark.no> In-reply-to: <20100212194604.GA73961@icarus.home.lan> References: <20100211190652.6a66c618.torfinn.ingolfsen@broadpark.no> <20100211192515.GB13854@icarus.home.lan> <20100212132947.eb2af3d0.torfinn.ingolfsen@broadpark.no> <20100212131117.GA51905@icarus.home.lan> <20100212174452.2140cd72.torfinn.ingolfsen@broadpark.no> <20100212194604.GA73961@icarus.home.lan> 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: Sat, 13 Feb 2010 18:50:35 -0000 On Fri, 12 Feb 2010 11:46:04 -0800 Jeremy Chadwick wrote: > override this though! :-) ), which -- assuming it works -- should > solve your problem. We'll see. The box rebooted again last night (see another thread on this mailing list), so now I have added kern.timecounter.hardware=ACPI-safe to /etc/sysctl.conf, just in case it reboots again. > Technical footnote: I wish I understood 1) the difference between > ACPI-safe and ACPI-fast, and 2) how the system or OS "ranks" the I'm still wondering why this machine doesn't have ACPI-fast: oot@kg-f2# sysctl kern.timecounter.choice kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) dummy(-1000000) While my workstation do: tingo@kg-v2$ sysctl kern.timecounter.choice kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0) dummy(-1000000) and anaother machine: root@kg-quiet# sysctl kern.timecounter.choice kern.timecounter.choice: TSC(800) ACPI-fast(1000) i8254(0) dummy(-1000000) and another: root@kg-vm# sysctl kern.timecounter.choice kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) dummy(-1000000) Probably a BIOS / acpi problem. -- Torfinn