calcru went backwards on 7 stable

[Dimitar Vasilev]

Thanks in

2008/7/24 Dimitar Vasilev <dimitar.vassilev at gmail.com>

>
>
> 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.
>>
> Hello,
I did kgdb print_cpu ticks today.
It says
(kgdb) print cpu_ticks
$1 = (cpu_tick_f *) 0xffffffff8077d340 <rdtsc>
This means that kernel is using tsc discipline actually imho.
Could someone confirm this?