calcru went backwards on 7 stable

Kris Kennaway kris at FreeBSD.org
Thu Jul 24 13:42:49 UTC 2008


Dimitar Vasilev wrote:
>> The "calcru went backwards" message can have two causes:
>>
>> 1) Your time counter really went backwards and is too broken to use.
>>
>> 2) Something caused clock interrupts to be delayed for extremely long
>> periods of time.  This happens if you break to DDB for example.  It can also
>> happen if there are kernel bugs, maybe in a driver etc.  Try to enable
>> additional debugging (WITNESS, INVARIANTS, etc; see the developers handbook)
>> and see where it gets you.
>>
>> Kris
>>
>> _______________________________________________
>> freebsd-questions at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "
>> freebsd-questions-unsubscribe at freebsd.org"
>>
> Thanks Kris,
> 
> Last time I tried to set the date there was a problem with the year  - I
> could not set the date beyond 2007

That doesn't sound like a FreeBSD bug.

> Also HZ were 2000 instead of 1000, but at that time machine was a
> uniprocessor one.

HZ=1000 by default, so are you saying you set it to 2000?

Kris


More information about the freebsd-questions mailing list