From owner-freebsd-questions Fri Sep 13 13:42: 9 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D369A37B400 for ; Fri, 13 Sep 2002 13:42:05 -0700 (PDT) Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EF9043E4A for ; Fri, 13 Sep 2002 13:42:05 -0700 (PDT) (envelope-from kylebutt@myrealbox.com) Received: from user-112vpc6.biz.mindspring.com ([66.47.229.134] helo=TriGem350) by maynard.mail.mindspring.net with esmtp (Exim 3.33 #1) id 17pxGN-0007Qh-00; Fri, 13 Sep 2002 16:42:03 -0400 Received: from TriGem350 (localhost [127.0.0.1]) by TriGem350 (8.12.5/8.12.5) with ESMTP id g8DEgPgo058901; Fri, 13 Sep 2002 14:42:26 GMT (envelope-from kylebutt@myrealbox.com) Received: (from kyle@localhost) by TriGem350 (8.12.5/8.12.5/Submit) id g8DEfN3V058887; Fri, 13 Sep 2002 14:41:23 GMT X-Authentication-Warning: TriGem350: kyle set sender to kylebutt@myrealbox.com using -f Date: Fri, 13 Sep 2002 14:40:22 +0000 From: Kyle Butt To: Daniel Rock Cc: freebsd-questions@freebsd.org Subject: Re: Clock runs too fast Message-ID: <20020913144022.GB58693@TriGem350> Mail-Followup-To: Daniel Rock , freebsd-questions@freebsd.org References: <20020907231952.A5525@attbi.com> <3D7B4638.1060007@t-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D7B4638.1060007@t-online.de> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 08, 2002 at 02:44:40PM +0200, Daniel Rock wrote: > Craig Rodrigues schrieb: > > >Hi, > > > >I have been having this problem with -current for the past 2 weeks now > >(I am new to -current and just started using it 2 weeks ago). > >I just did a cvsup and rebuilt the kernel and rebuilt the world. > > > >My clock seems to be running too fast, and I keep resetting it > >with ntpdate. > > > >[...] > > > >Now the clock seems to run at a more reasonable rate. > > > >Is there a problem with the ACPI code or with my > >hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). > > > >How can I default to i8254 as my default timer? Is there > >something I should put in device.hints? > > > I had similar problems with a Gigabyte GA-5AX (also with ALi Aladdin V > chipset). Without setting > debug.acpi.disable = "timer" > the clock runs twice as fast as it should be. This problem seems to be > introduced in the ACPI update around July 2001. I didn't find any > solution other than disabling ACPI timecounter. That setting disappeared a while ago. I found another solution to the twice as fast problem. I doubled machdep.acpi_timer_freq in /etc/sysctl.conf I started by halving that, but that made my clock go 4x. Yikes. So I doubled it. If anyone knows how to set this at boot, please tell me. machdep.acpi_timer_freq=7159090 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message