Daniel Rock schrieb:
>My kernel war relatively recent at the time of last boot - build
>around March 2nd from -CURRENT sources a few hours before.
>
>If someone runs -CURRENT with default HZ of 100 and moans 247 days
>later, his -CURRENT cannot be called -CURRENT any more...
>
>I am now running a
Bill Fenner schrieb:
>
> I had the same symptoms (drifting about 2 minutes an hour) on sources
> before April 17 or so. Since then, ntpd has only logged 5 time updates,
> as opposed to 3 per hour.
>
The drift wasn't visible immediately, but only after the "magical" 49.7 days
or 2^31 clock ticks.
In message <[EMAIL PROTECTED]>, Daniel Rock writes:
>Poul-Henning Kamp schrieb:
>>
>> When was your source tree from on that kernel ?
>>
>> I'm not too confident in your diagnosis, mostly because we don't
>> have a counter like you describe :-)
>>
>> My guess is that ntpd get confused.
>>
>> P
Poul-Henning Kamp schrieb:
>
> When was your source tree from on that kernel ?
>
> I'm not too confident in your diagnosis, mostly because we don't
> have a counter like you describe :-)
>
> My guess is that ntpd get confused.
>
> Please try a newer kernel, a number of bug(lets) have been fixe
I had the same symptoms (drifting about 2 minutes an hour) on sources
before April 17 or so. Since then, ntpd has only logged 5 time updates,
as opposed to 3 per hour.
Bill
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, 1 May 2002, Poul-Henning Kamp wrote:
> When was your source tree from on that kernel ?
>
> I'm not too confident in your diagnosis, mostly because we don't
> have a counter like you describe :-)
>From kern_clock.c:
%%%
int ticks;
%%%
but this is treated as an cyclic counter so its
When was your source tree from on that kernel ?
I'm not too confident in your diagnosis, mostly because we don't
have a counter like you describe :-)
My guess is that ntpd get confused.
Please try a newer kernel, a number of bug(lets) have been fixed
since march.
If it happens again, please e
On Tuesday 30 October 2001 06:17 pm, Dreamtime.net Inc. wrote:
> A while back I read a thread regarding clock drift. We are now having the
> same problem. Does anyone know what the remedy is for this? Thanks.
>
> Sincerely,
>
> Stephen H. Kapit
>
I had the same problem a couple of months ago. Try
