Subject: kern/24207: ntpd does not work properly on MP systems.
To: None <gnats-bugs@gnats.NetBSD.org>
From: None <christos@zoulas.com>
List: netbsd-bugs
Date: 01/23/2004 10:05:25
>Number: 24207
>Category: kern
>Synopsis: ntp does not keep proper time on MP systems.
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jan 23 15:06:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: Christos Zoulas
>Release: NetBSD 1.6ZG
>Organization:
Fuzzy and Furry, Inc.
>Environment:
System: NetBSD mx1.twosigma.com 1.6ZG NetBSD 1.6ZG (TWOSIGMA.MP) #13: Thu Dec 11 12:46:28 EST 2003 christos@mx1.twosigma.com:/usr/src/sys/arch/i386/compile/TWOSIGMA.MP i386
Architecture: i386
Machine: i386
>Description:
On a multi-processor system, ntp does not appear to be able
to sync to other ntp servers, and the clock keeps bouncing
around.
>How-To-Repeat:
Configure an ntp server on an MP system. Look at the ntp
statistics. On the same system, boot a single processor
kernel. Watch it work.
Look at the large offsets:
remote local st poll reach delay offset disp
=======================================================================
=WWW.UREGINA.CA 166.84.149.248 2 512 377 0.11034 2.943641 0.00929
*nist1-ny.glasse 166.84.149.248 1 512 377 0.01353 3.121874 0.00735
=clepsydra.dec.c 166.84.149.248 1 512 377 0.09393 2.938217 0.00928
=otc1.psu.edu 166.84.149.248 1 512 377 0.02994 3.088238 0.00740
=louie.udel.edu 166.84.149.248 2 512 377 0.01747 3.273659 0.00734
=filbert.cc.colu 166.84.149.248 2 512 377 0.01768 3.113442 0.00739
=ntp2.usno.navy. 166.84.149.248 1 512 377 0.21408 2.968513 0.00928
=ftp.jensenresea 166.84.149.248 1 512 377 0.01797 2.939460 0.00928
=clock.isc.org 166.84.149.248 2 512 377 0.08876 3.105656 0.00735
=time.nrc.ca 166.84.149.248 2 512 377 0.05721 3.117920 0.00735
=seismo.cmr.gov 166.84.149.248 2 512 377 0.08006 3.257980 0.00737
>Fix:
Dunno, looking.
>Release-Note:
>Audit-Trail:
>Unformatted: