Date: Thu, 30 Dec 2004 17:06:43 -0600 From: Kevin Kinsey <kdk@daleco.biz> To: FreeBSD Stable <stable@freebsd.org> Cc: dtalk-ml@prairienet.org Subject: Re: clock running fast Message-ID: <20041230230643.GA87010@ezekiel.daleco.biz> In-Reply-To: <20041230222903.GA16002@archangel.daleco.biz> References: <20041230222903.GA16002@archangel.daleco.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
> [ rc.conf and ntp.conf snipped ] > > Thank you for the suggestions. Unfortunately, I've been through all > that, including the rude values of minpoll and maxpoll, using multiple > servers, and starting with a fresh drift file. I'm pretty sure ntpd > isn't the problem. In addition, the hardware clock itself appears to be > plenty accurate, as it is always correct within a second or two when I > check it directly in BIOS ... and two other 5.3-STABLE hosts on the same > network, with the same ntpd configuration, but on different hardware, do > not have this problem, which began when I updated (reinstalled) to > 5.3-STABLE from 5.2. > > - -- > David Talkington > dtalk-ml@prairienet.org I apparently misposted this earlier, my apologies. Have you tried all possible values for kern.timecounter.hardware? #sysctl kern.timecounter.choice My most recent encounter with this issue, a K6-2/500 on an Asus P5A mobo, needed "i8254". HTH, Kevin Kinsey
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041230230643.GA87010>