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
>         dmesg

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 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.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to