Date: Sat, 04 May 2002 13:11:10 +0200 From: Daniel Rock <D.Rock@t-online.de> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: current@FreeBSD.ORG Subject: Re: clock drift in -CURRENT Message-ID: <3CD3C1CE.4010909@t-online.de> References: <64858.1020263148@critter.freebsd.dk> <3CD0489F.D79EFF3F@t-online.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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. I had run the kernel now for over 2^31 clock ticks and had no drifting problem so far. I will now set HZ back to 500 - let's see what happens in 50 days... Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CD3C1CE.4010909>