From owner-freebsd-current Thu Jan 23 12:51:53 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2622337B401; Thu, 23 Jan 2003 12:51:52 -0800 (PST) Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D4AC43F1E; Thu, 23 Jan 2003 12:51:51 -0800 (PST) (envelope-from patrick@137.org) Received: from 137.org (gfxn2.vrac.iastate.edu [129.186.232.116]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id 943A71F; Thu, 23 Jan 2003 14:51:53 -0600 (CST) Message-ID: <3E3055EF.8010808@137.org> Date: Thu, 23 Jan 2003 14:51:59 -0600 From: Patrick Hartling Reply-To: patrick@137.org User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin Cc: freebsd-current@freebsd.org Subject: Re: Time keeping problems with 5.0-RELEASE References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG That fixed it. Thanks a bunch. :) -Patrick John Baldwin wrote: > On 23-Jan-2003 Patrick Hartling wrote: > >>I just updated a 4.7-STABLE system (last rebuilt using sources from >>Jan 7, 2003) to 5.0-RELEASE, and now the system clock is going nuts. >>I had the same problem when I updated from 3-STABLE to 4-STABLE quite >>a while back. To solve the problem then, I added the following to my >>kernel configuration file: >> >> device apm0 at nexus? disable flags 0x20 >> >>For my 5.0 kernel configuration, I have: >> >> device apm >> >>In /boot/device.hints, I have: >> >> hint.apm.0.disabled="1" >> hint.apm.0.flags="0x20" >> >>Unfortunately, this isn't working. Is there something different I need >>to do for 5.0? Looking in NOTES for information about APM, I see a >>reference to a sysctl variable kern.timecounter.method, but that doesn't >>seem to be a valid oid in 5.0. I don't think this system (a cheap, old >>Cyrix MediaGX-based computer) supports ACPI. At the very least, ACPI >>isn't enabled by default at boot time as it is on my Athlon system. > > > The sysctl is now kern.timecounter.hardware. For example: > > >>sysctl kern.timecounter.hardware > > kern.timecounter.hardware: ACPI-safe > > If it is currently set to 'tsc', try changing it to 'i8254' and see if > it works better. If so, you can stick that in /etc/sysctl.conf. > -- Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message