[ntp:questions] ntpd wedged again

A C agcarver+ntp at acarver.net
Fri Feb 10 07:10:58 UTC 2012

On 2/9/2012 19:07, A C wrote:
> So far so good, it's running with reasonable offsets and jitter (PPS not
> yet enabled).
> But this is new to me in the logs:
> 10 Feb 01:41:37 ntpd[242]: ts_min 1328838097.185664676 ts_prev
> 1328838097.185550676 ts 1328838097.189745353
> 10 Feb 01:41:37 ntpd[242]: sys_fuzz 114000 nsec, this fuzz 0.000099410
> 10 Feb 01:41:37 ntpd[242]: get_systime prev result 0xd2def451.30cccb9b
> is 0.000780166 later than 0xd2def451.3099aa99

I still would like to know what this means since I see it once in a 
while but I just had a thought:

Up until the snprintf bugfix, I had never seen this fuzz entry in the 
logs.  I'm betting, given the ASCII size of the numbers, they were being 
generated and fed to dtoa() which then would explode and lock up ntpd 
and so the entries would never make it to the log file because the whole 
process was wedged.

More information about the questions mailing list