Date: Sun, 27 Feb 2000 09:31:42 -0500 From: Paul Murphy <pnmurphy@home.com> To: Ben Smithurst <ben@scientia.demon.co.uk>, freebsd-questions <freebsd-questions@FreeBSD.ORG> Subject: Re: My machine prints "calcru: negative time..." Message-ID: <38B9354E.879F116B@home.com> References: <0ff301bf8096$dc1cfc00$0200000a@danco.home> <38B917D8.B6DA7DB5@home.com> <20000227132953.A47478@strontium.scientia.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > It is actually a 486DX2/66. Is the 'Timecounter' settable in the > > kernel? > > I think only 586s and above have a TSC, so the machdep.tsc_freq sysctl may > not exist, or may be meaningless. > You must be right, 'sysctl -a' does not show a 'machdep.tca_freq'. So back to the original question: How to trace the root cause of the calcru problem? Setting kern.timecounter.method=0 -> 1 seems to have worked, does anyone know how much of a performance hit [as stated in the FAQ] this costs? 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?38B9354E.879F116B>