Date: Thu, 1 Dec 2005 21:06:09 -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: <54db43990512011806x2ab9a58ayde78b97c2f90b66a@mail.gmail.com> In-Reply-To: <200512012036.jB1Kaqo08304@akiva.homer.att.com> References: <200512012036.jB1Kaqo08304@akiva.homer.att.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/1/05, J. W. Ballantine <jwb@homer.att.com> wrote: > > I running 6-RELEASE as a guest under vmware 5.5 and I'm having > problems with the clock going backwards. I'm getting the message (sample= ): > > calcru: runtime went backwards from 10542602 usec to 10542600 usec for pi= d > 13924 > (vmware-guestd) [etc.] > > Is this bsd or vmware related, and any way to fix it? > I don't have direct experience with this, but the reports I've seen indicate that vmware has clock problems with both FreeBSD and Linux.=20 One suggestion is that in vmware, set host.useFastclock =3D "FALSE" in the .vmx file. Another suggestion is that in FreeBSD 6.0 you can try setting 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. It has also been recommended to set "options HZ=3D1000" in your kernel configuration. Hope that helps, and if I got any of that wrong, someone please correct me! - 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?54db43990512011806x2ab9a58ayde78b97c2f90b66a>