calcru went backwards on 7 stable

[Dimitar Vasilev]

2008/7/24 Kris Kennaway <kris at freebsd.org>:

> 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
>
Thanks Kris,
I appreciate your help.
I'm aware that bios bugs are not related to FreeBSD.
Machine we're speaking about is one of the official mirrors for FreeBSD in
Bulgaria.
System was running fine with HZ=2000 from 2005 to 2007 with a single CPU and
5-stable series.
After I moved back to Sofia we moved it to 7-stable, 1000 HZ by default and
added a second CPU.
I'm trying to isolate the problem with the help of all subscribers - I don't
have frequent access to the server room which leads to
delayed troubleshooting.
Will change CMOS battery and update bios as a start.
Thanks for helping.

Best regards,
Dimitar Vassilev