[ntp:questions] Can't wait on Refclock: err=22, 'Invalid argument'

Charles Elliott elliott.ch at verizon.net
Wed Jul 31 11:03:15 UTC 2013


Does anyone know from where this NTPD error comes from?

 

Event Viewer output:

	
System

 

		

-

Provider

 

			
[ Name] 

NTP

 

		

-

EventID

1


	
Level

2

				

 

		
	
Task

0

 


 			
	
Keywords

0x80000000000000


-

EventData

				

 

			
Can't wait on Refclock: err=22, 'Invalid argument'

 

 

Using AstroGrep 4.2.5, for Windows, a search on 'Can't wait on Refclock' in
ntp-dev-4.2.7p375 in files *.c and 

*.h returns nothing.  Searching on the individual words, 'Can't', 'wait',
and 'Refclock' returns a few lines

each, but nothing that seems related to this error.

 

What is happening is that the MR-350P, an inexpensive GPS device with a PPS
output that works well and

unceasingly when connected to a Windows 7 machine thru the RS-232 port,
fails (with the above error)

about every 8 hours when attached to a Windows 8 machine using either one of
two RS-232 to USB

adapters.  A BU-353-S4 attached to the Win 8 system natively thru the USB
port used to run forever, 

albeit with inaccurate time.  When I stop NTPD and attach SiRFDemo to the
port the MR-350P is connected

to, the NMEA data is perfect.  

 

There have been a few problems with the USB ports after a recent spate of
Windows automatic updates, so this problem could be related to that.

 

Charles Elliott



More information about the questions mailing list