From owner-freebsd-current Sun Feb 22 09:16:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11775 for freebsd-current-outgoing; Sun, 22 Feb 1998 09:16:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11770 for ; Sun, 22 Feb 1998 09:16:42 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id JAA27163; Sun, 22 Feb 1998 09:16:00 -0800 (PST) To: John Hay cc: freebsd-current@FreeBSD.ORG Subject: Re: clock code working properly in -current? In-reply-to: Your message of "Sat, 22 Feb 1998 14:34:22 +0200." <199802221234.OAA11729@zibbi.mikom.csir.co.za> Date: Sun, 22 Feb 1998 09:16:00 -0800 Message-ID: <27159.888167760@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. That's pretty interesting since I know of a dual PII box at a friend's place of work that's been doing *exactly* this ever since SMP entered -current; it's never worked properly. You know how hard it is to benchmark a machine who's clock runs twice as fast, too? :-) I wonder if this is a bug which has been latent since the beginning but only bites some people. We asked Steve Passe if he wanted to borrow the box in question but he was too busy. :( Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message