Date: Wed, 4 May 2005 15:18:03 -0700 (PDT) From: Luke Dean <LukeD@pobox.com> To: Ryan Winograd <rylwin@houston.rr.com> Cc: freebsd-questions@freebsd.org Subject: Re: Clock running fast Message-ID: <20050504151359.U72230@border.crystalsphere.multiverse> In-Reply-To: <4279448F.4010103@houston.rr.com> References: <42792740.3040501@houston.rr.com> <34d0f02f0868350c3c07570e3a73ceef@mac.com> <4279448F.4010103@houston.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 4 May 2005, Ryan Winograd wrote: > Charles Swiger wrote: > >> On May 4, 2005, at 3:49 PM, Ryan Winograd wrote: >> >>> I recently noticed that the system clock on a machine i recently set up is >>> running very quickly, about 2x realtime by my measuring. What can i do to >>> solve/investigate this problem? What information would be helpful? >> >> >> Try changing the kern.timecounter.hardware sysctl; you can look at the >> available choices via: >> >> sysctl kern.timecounter.choice >> > > Thanks for all the advice everyone. The solution was changing the > kern.timecounter.hardware sysctl to i8254 (was ACPI-safe). I was using NTP, > but when the clock is at 2x even having cron run ntp every minute is too > innacurate. > > Thx again! > Ryan I wish I'd known about that sysctl when I had this problem on my last system! I tried ntp, but having ntp constantly resetting the clock just added new problems. Thanks for sharing the outcome with us.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050504151359.U72230>