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.
>> Please try a newer kernel, a number of bug(lets) have been fixed
>> since march.
>> If it happens again, please email me the output of:
>> ntpdc -c peer
>> ntpdc -c loopi
>> ntpdc -c kerni
>My kernel war relatively recent at the time of last boot - build
>around March 2nd from -CURRENT sources a few hours before.
Right, but look at a cvs log src/sys/kern/kern_tc.c... I've fixed
at least one bug in the NTP steering since then.
>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 an up-to-date -CURRENT. I have set HZ=10000, so
>I don't have to wait another 50 days. Hope this high HZ value has
>no negative impact on the test.
>I will inform you in 3 days if anything strange happens again.
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message