From owner-freebsd-stable@FreeBSD.ORG Thu Oct 16 09:25:12 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B105216A4C3 for ; Thu, 16 Oct 2003 09:25:12 -0700 (PDT) Received: from catseye.mine.nu (d154-5-164-0.bchsia.telus.net [154.5.164.0]) by mx1.FreeBSD.org (Postfix) with SMTP id 8BC9643FF9 for ; Thu, 16 Oct 2003 09:25:11 -0700 (PDT) (envelope-from catseye@catseye.mine.nu) Received: (qmail 75843 invoked by uid 1001); 16 Oct 2003 16:27:16 -0000 Date: Thu, 16 Oct 2003 09:27:16 -0700 From: Chris Pressey To: "Kevin Oberman" Message-Id: <20031016092716.2a2b9c3c.cpressey@catseye.mine.nu> In-Reply-To: <20031016150926.C45F25D07@ptavv.es.net> References: <3F8E9CA6.4080502@lexisnexis.com> <20031016150926.C45F25D07@ptavv.es.net> Organization: Cat's Eye Technologies X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: greg.panula@lexisnexis.com cc: freebsd-stable@freebsd.org Subject: Re: 5.1 RELEASE: clock running wild? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 16:25:12 -0000 On Thu, 16 Oct 2003 08:09:26 -0700 "Kevin Oberman" wrote: > As stated, V5.x questions should go to freebsd-current@, not stable. FWIW, I get this too on 4.9-RC (Oct 13th). (Until now I thought it was a hardware problem.) > The problem you are seeing has shown up on a few mobos. The most > common is the ASUS P5A, but others have also reported the issue. > It appears to be a bug in the board ACPI firmware. The clock runs at > exactly double speed. This describes my situation exactly (ASUS P5A, ACPI, clock x2) > The problem is bad enough that simply using ntp > is inadequate, but it is easily worked around. > > Edit /etc/sysctl.conf to contain > "kern.timecounter.hardware="TSC". This will make the clock run > correctly after a reboot. Trying this, upon boot, I get: sysctl: kern.timecounter.hardware: Invalid argument Leaving out the quotes around TSC seems to work though. Beautiful, no more playing around with timed/ntpd/clockspeed! Thanks. -Chris