On Mon, Jun 30, 2008 at 7:38 AM, Bob Johnson <[EMAIL PROTECTED]> wrote:
> On 6/30/08, David Allen <[EMAIL PROTECTED]> wrote:
>> I've been seeing errors like the following appearing:
>>
>> Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 261
>> usec to 258 usec for pid 516 (devd)
> [
I've been seeing errors like the following appearing:
Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 261
usec to 258 usec for pid 516 (devd)
Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 4976
usec to 4926 usec for pid 367 (pflogd)
Jun 30 03:13:57 ford kernel:
On 6/30/08, David Allen <[EMAIL PROTECTED]> wrote:
> I've been seeing errors like the following appearing:
>
> Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 261
> usec to 258 usec for pid 516 (devd)
[...]
> Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 486
> us
On 12/1/05, Bob Johnson <[EMAIL PROTECTED]> wrote:
>
> sysctl kern.MUMBLE.timecounter=TSC
>
> 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
On 12/1/05, J. W. Ballantine <[EMAIL PROTECTED]> 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 pid
> 13924
> (vmware-
