>Number:         7602
>Category:       port-alpha
>Synopsis:       1.4 xntpd says "Previous time adjustment incomplete" on alpha
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-alpha-maintainer (NetBSD/alpha Portmaster)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 18 11:35:01 1999
>Last-Modified:
>Originator:     Chris G. Demetriou
>Organization:
Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html
Disclaimer: Not speaking for NetBSD, just expressing my own opinion.
>Release:        
>Environment:
System: NetBSD alpha 1.4 NetBSD 1.4 (GENERIC) #1: Sat May  8 11:37:01 PDT 1999     ross@netbsd.org:/usr/src/sys/arch/alpha/compile/GENERIC alpha

>Description:
	After upgrading one of my alphas from 1.3F to 1.4, xntpd started
	complaining about:

May 18 10:47:59 alpha xntpd[142]: 5.93c 3-NetBSD Wed Aug 12 10:05:25 EDT 1998 (1)
May 18 10:47:59 alpha xntpd[142]: tickadj = 40, tick = 976, tvu_maxslew = 40920, est. hz = 1024
May 18 10:47:59 alpha xntpd[142]: precision = 762 usec
May 18 10:52:49 alpha xntpd[142]: synchronized to 10.1.1.5, stratum=2
May 18 10:53:00 alpha xntpd[142]: time reset (step) 10.776500 s
May 18 10:53:00 alpha xntpd[142]: synchronisation lost
May 18 10:58:19 alpha xntpd[142]: synchronized to 10.1.1.5, stratum=2
May 18 10:58:24 alpha xntpd[142]: Previous time adjustment incomplete; residual -0.001640 sec
May 18 10:58:26 alpha xntpd[142]: Previous time adjustment incomplete; residual -0.001640 sec
May 18 10:58:28 alpha xntpd[142]: Previous time adjustment incomplete; residual -0.001560 sec
May 18 10:58:40 alpha last message repeated 6 times
May 18 10:58:42 alpha xntpd[142]: Previous time adjustment incomplete; residual -0.001600 sec
May 18 10:58:48 alpha last message repeated 3 times
May 18 10:58:50 alpha xntpd[142]: Previous time adjustment incomplete; residual -0.001560 sec
May 18 10:59:02 alpha last message repeated 6 times

	
	After those messages, it seems to have become quiet.

	My intuition says that while those messages aren't indicative of
	a fatal or "really really bad" condition, they indicate that adjtime()
	is doing _something_ that xntp doesn't expect.  I'm reporting this
	(it may be a non-bug) because i've never seen those messages before,
	on any platform, which makes me think something changed for
	the worse.

>How-To-Repeat:
	Run xntpd?  (It doesn't seem quite that easy, as the next
	time I booted the box, it did not report the same problem adjusting
	the time (though neither did it have to step the time at startup.)

>Fix:
	I think the right way to 'fix' this one is for somebody with an
	understanding of how adjtime is supposed to work to look through
	the clock code to make sure that the right things are happening on
	the alpha.
>Audit-Trail:
>Unformatted: