Date: Thu, 1 Dec 2005 21:15:10 -0500 From: Bob Johnson <fbsdlists@gmail.com> To: "J. W. Ballantine" <jwb@homer.att.com> Cc: bobo1009@mailtest1.eng.ufl.edu, freebsd-questions@freebsd.org Subject: Re: calcru: runtime went backwards Message-ID: <54db43990512011815p3b355c9cne10a9f3b1f676479@mail.gmail.com> In-Reply-To: <54db43990512011806x2ab9a58ayde78b97c2f90b66a@mail.gmail.com> References: <200512012036.jB1Kaqo08304@akiva.homer.att.com> <54db43990512011806x2ab9a58ayde78b97c2f90b66a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/1/05, Bob Johnson <fbsdlists@gmail.com> wrote: > > sysctl kern.MUMBLE.timecounter=3DTSC > > except I don't know what "MUMBLE" is in 6.0. > > sysctl -a | grep timecounter > > should reveal it, though. And if it is already "TSC", try "i8254", > I've seen both recommended. There are probably other possibilities > (e.g. "ACPI-safe" seems to be the default these days) but as I said, I > have no direct experience with vmware. In 5.x, this would be sysctl kern.timecounter.hardware=3DTSC but I don't know about 6.0 Good luck. - Bob -- Spammers: please send mail to bobo1009@mailtest1.eng.ufl.edu and help me tune my spam filters!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54db43990512011815p3b355c9cne10a9f3b1f676479>