Date: Wed, 28 Jun 2000 16:32:38 +0200 From: Andreas Persson <pap@garen.net> To: freebsd-stable@FreeBSD.ORG Subject: Re: microuptime() going backwards Message-ID: <20000628163236.A70918@sophocles> In-Reply-To: <200006280321.UAA00490@mass.osd.bsdi.com>; from msmith@freebsd.org on Tue, Jun 27, 2000 at 08:21:18PM -0700 References: <20000627120348.B5328@sydney.worldwide.lemis.com> <200006280321.UAA00490@mass.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 27, 2000 at 08:21:18PM -0700, Mike Smith wrote: >I explained this to you at Usenix, actually. It has nothing to do with >APM, it has to do with the selection of clocks available with/without APM >compiled into the kernel - there is probably either a bug in the TSC >hardware on this CPU, or (more likely) a bug in the timecounter code >(since people see this on !APM systems already). Setting the sysctl kern.timecounter.method to 1 seems to have solved this on one of my 4.0-RELEASE boxes. No microuptime() messages for almost 3 weeks now. >-- >\\ Give a man a fish, and you feed him for a day. \\ Mike Smith >\\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org >\\ and he'll hate you for a lifetime. \\ msmith@cdrom.com -- Andreas Persson pap@garen.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000628163236.A70918>