Date: Thu, 25 Oct 2001 17:40:13 -0400 From: "Doug Reynolds" <mav@wastegate.net> To: "questions@FreeBSD.ORG" <questions@FreeBSD.ORG>, "Randy Pratt" <rpratt@ezwv.com> Subject: Re: microuptime and kern.timecounter.method Message-ID: <20011025214131.7AA0937B447@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
On Tue, 23 Oct 2001 14:52:48 -0400, Randy Pratt wrote: >I resurrected my old 486DX2-66V for some lightweight server duties and >installed 4.4-RELEASE. I would see the occasional message like: > > microuptime() went backwards (345.292246 -> 345.-695042607) > >The archives suggested recompiling the kernel to remove the apm option. That >did not seem to do the trick. However, another post suggested: > > sysctl kern.timecounter.method=1 > >So far, things seem to be stable with no microuptime() messages (20 hrs). >Now I'm searching for more information on what this accomplished and what >other options are available for the kern.timecounter.method. The man page >for sysctl didn't reference this variable. basically the kernel pulls the time from either the bios or the realtime clock.. I can't remember which. basically one of them is a _lot_ more accurate. the timecounter just uses a different src if i am corrent --- doug reynolds | the maverick | mav@wastegate.net 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?20011025214131.7AA0937B447>