Date: Thu, 17 Jan 2002 09:05:33 -0500 From: "Predius" <predius@netzero.net> To: <freebsd-questions@freebsd.org> Subject: Re: racing clock Message-ID: <004301c19f60$07abf030$fa01a8c0@ABERRATION> References: <20020117170112.A25151@BlueSkyFrog.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
Yup, had an older Dell Dimension which would do the same thing, ntpd couldn't adjust enough to correct for it. There is a sysctl that you can use to change which timer your system runs off, switch it and you'll be fine. kern.timecounter.hardware: i8254 If my dmesg wasn't wiped out by imcp bandwidth limiting messages (why do those go to the dmesg log by default?!) I'd get the name of the other timer. Net result, switch the one you're using and you should be all set. Joshua Coombs ----- Original Message ----- From: "Nick Slager" <ns@BlueSkyFrog.COM> To: <freebsd-questions@freebsd.org> Sent: Thursday, January 17, 2002 2:01 AM Subject: racing clock > I have a machine which appears to be in a great hurry: > > orange$ date;sleep 1;date;sleep 1;date > Fri Jan 18 06:39:10 EST 2002 > Fri Jan 18 06:39:23 EST 2002 > Fri Jan 18 06:39:35 EST 2002 > > The machine is an oldish Acer. Until recently this box ran linux with > no apparent issues. dmesg(8) attached; particularly worrying is the > alleged cpu speed... > > Anyone seen this before and can suggest a possible solution? Please CC > me on replies as I'm not on -questions. > > Thanks, > > > Nick > > -- > Excuse of the day: > /dev/clue was linked to /dev/null > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004301c19f60$07abf030$fa01a8c0>