Date: Sun, 22 Feb 1998 13:39:47 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: John Hay <jhay@mikom.csir.co.za> Cc: freebsd-current@FreeBSD.ORG Subject: Re: clock code working properly in -current? Message-ID: <11056.888151187@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 22 Feb 1998 14:34:22 %2B0200." <199802221234.OAA11729@zibbi.mikom.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199802221234.OAA11729@zibbi.mikom.csir.co.za>, John Hay writes: >Hi, > >The new clock code seems to be broken (for me at least) or is there >something that I must do/set/configure to make things work again? > >With kernels build today, both my 90MHz Pentium UP machine and my 266MHz >PII SMP machine gain a lot of time. The Pentium gain about 2 seconds per >minute and the SMP machine about 1 second per minute. Needless to say >xntpd can't cope with a frequency error that big. Previously xntpd and >ntp-4 reported a 24ppm error on the Pentium and a -297ppm error on the >SMP machine. Yes, please boot with '-v', and send me the dmesg output & the output of sysctl -a. Add CLK_USE_TSC_CALIBRATION and CLK_USE_I8254_CALIBRATION to your kernel, and repeat. >One other strange thing that I noticed is that "systat -vmstat" on the >SMP machine reports the clk0 interrupt rate as 50 and the rtc0 rate as >64, while on the UP machine it is still reported as 100 and 128 like >before. This is unrelated I belive. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" 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?11056.888151187>