From owner-freebsd-questions@freebsd.org Tue Aug 16 11:20:22 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53159BBBEF1 for ; Tue, 16 Aug 2016 11:20:22 +0000 (UTC) (envelope-from Ephaeton@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BCD5E1688 for ; Tue, 16 Aug 2016 11:20:21 +0000 (UTC) (envelope-from Ephaeton@gmx.net) Received: from hephaistos.local ([188.193.147.216]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0M0LtB-1bLOPh38aD-00uZb8 for ; Tue, 16 Aug 2016 13:20:12 +0200 Received: by hephaistos.local (Postfix, from userid 1000) id 525B2297CDF6; Tue, 16 Aug 2016 13:20:02 +0200 (CEST) Date: Tue, 16 Aug 2016 13:20:02 +0200 From: "Martin S. Weber" To: freebsd-questions@freebsd.org Subject: Losing time like crazy (1s short per 10s) - how to investigate? Message-ID: <20160816112002.GA3083@hephaistos.local> Mail-Followup-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.6.1 (2016-04-27) X-Provags-ID: V03:K0:QAG7DEJn0OXccRHnwPRieY6XspoG6VFV77a9LfhtYKG2ftc2eZX 4eH6yYymUBVVDzglVPJXPwLZy5VvGa9GVyb1XuubunIDSXTYRM3AEtZ3Dtvd/gbQNJbCveR uUXy5navLU6J8YDIujpCKGurDWaG4X3FWqqEZrjPtAWoFQug0A/5mDHoZftHceFIu66Cj7G b0HKM/8oqMJ4pnJPzSARA== X-UI-Out-Filterresults: notjunk:1;V01:K0:zCZlebTSUXc=:WUaNH6ZuDivKFCF/NJcgfs b4Q6IsN5oknICvSG60iyiOoKeObGVCDHTOpsn7rZtU5/9Hb/4Ehhn3LCYTJeYwxfwOSuh0qaj dHH9ZwyMOkrwgJWNTfBCtIOUAmLH9vghNRM0RVR99JAxzX5+2oypNPcl3Venb2DHr2d7qCvwb wpUiUtBDX1y7QXHqW1s5G+GB2x0t5lkUJ53geGJkz0MJn08lph90/ORzevhAw2dUG50AAKuE5 e6WvRojIAdP1iryBb7WQmajTyn9PYohlptA149gPZCwnW9qQa5pNXFFVZLL9rVH9xp/M9pEpP EpGyTzhgJDp6RkqWA1iIbbaGJnZJuOubn2w260ly9DmsYWwWj/foaB4wtXet/rhNUbmJ7bNc5 LocQfBBXMDeYQPa9JKeqzH99KqwOdm04EVxupeJhibhEC3WIzECnan4xPnMVXMxYUqNWsPI2h r9W2TiIxVeq5a3x1XohzPC+b5WR/Ub6GqS7QNCK+RQ07mLzqexD5l7kz5Y9EVz2pYDN1mX45v n6Jsw5EsOZlGG1Mbsjt6/nNPZ+qS5wpbtZrnEgFfx9E+ZhR2X8hCupZJsGMhDkjWhWJ4Y3ZX1 1SHUi3p087TZu2lknCL4dyI3+ncB/rHyNlBWi4ovu0owvyl8cxRRni1riUZHtGm1ZaPusTDqd griFMFnv8MJ4wvh7wdS9almnTn12BsTz/tLT40aAUv3KjNNN56ZIICJoZ05m9sCz66PfZucHZ DWFkNAgjI2nn5DWZtx43xuITFWu7/FjZnt5AWbam4RNistX6auri6+kAK4w= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2016 11:20:22 -0000 This is on FreeBSD 10.3-RELEASE-p7. I've only noticed this today, so I'd suspect this is post the p7 update (although I haven't investigated in that direction yet). I'm losing roughly a second per 10 seconds wall time. Look at this crazy guy: # ntpd -q ; sleep 10; ntpd -q 16 Aug 13:12:52 ntpd[48425]: ntpd 4.2.8p8-a (1): Starting 16 Aug 13:12:52 ntpd[48425]: Command line: ntpd -q 16 Aug 13:12:52 ntpd[48425]: proto: precision = 0.230 usec (-22) 16 Aug 13:12:52 ntpd[48425]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): good hash signature 16 Aug 13:12:52 ntpd[48425]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): loaded, expire=2016-12-28T00:00:00Z last=2015-07-01T00:00:00Z ofs=36 16 Aug 13:12:52 ntpd[48425]: Listen and drop on 0 v6wildcard [::]:123 16 Aug 13:12:52 ntpd[48425]: Listen and drop on 1 v4wildcard 0.0.0.0:123 16 Aug 13:12:52 ntpd[48425]: Listen normally on 2 em0 10.10.1.79:123 16 Aug 13:12:52 ntpd[48425]: Listen normally on 3 lo0 [::1]:123 16 Aug 13:12:52 ntpd[48425]: Listen normally on 4 lo0 [fe80::1%2]:123 16 Aug 13:12:52 ntpd[48425]: Listen normally on 5 lo0 127.0.0.1:123 16 Aug 13:12:52 ntpd[48425]: Listening on routing socket on fd #26 for interface updates 16 Aug 13:12:54 ntpd[48425]: ntpd: time set +0.891676 s ntpd: time set +0.891676s 16 Aug 13:13:04 ntpd[48426]: ntpd 4.2.8p8-a (1): Starting 16 Aug 13:13:04 ntpd[48426]: Command line: ntpd -q 16 Aug 13:13:04 ntpd[48426]: proto: precision = 0.229 usec (-22) 16 Aug 13:13:04 ntpd[48426]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): good hash signature 16 Aug 13:13:04 ntpd[48426]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): loaded, expire=2016-12-28T00:00:00Z last=2015-07-01T00:00:00Z ofs=36 16 Aug 13:13:04 ntpd[48426]: Listen and drop on 0 v6wildcard [::]:123 16 Aug 13:13:04 ntpd[48426]: Listen and drop on 1 v4wildcard 0.0.0.0:123 16 Aug 13:13:04 ntpd[48426]: Listen normally on 2 em0 10.10.1.79:123 16 Aug 13:13:04 ntpd[48426]: Listen normally on 3 lo0 [::1]:123 16 Aug 13:13:04 ntpd[48426]: Listen normally on 4 lo0 [fe80::1%2]:123 16 Aug 13:13:04 ntpd[48426]: Listen normally on 5 lo0 127.0.0.1:123 16 Aug 13:13:04 ntpd[48426]: Listening on routing socket on fd #26 for interface updates 16 Aug 13:13:06 ntpd[48426]: ntpd: time set +1.218972 s ntpd: time set +1.218972s This is a CRAZY amount of skew. I've never noticed this before -- and I have tmux with a clock running on various servers I'm logged in; And a chiming wall clock whose skew I check vs. my system clock. This is a new "feature" - I suspect an unfortunate interaction with FreeBSD-EN-16:13.vmbus. Running ntpd or not doesn't make a difference, interestingly, I'm still losing time even with ntpd on (above example is with ntpd not running). How can I investigate what might be the source of the problem? What info can I give that might help more informed people jump to the correct conclusion what's off? Here's what I've lost since starting to write this email: 16 Aug 13:17:58 ntpd[48461]: Listening on routing socket on fd #26 for interface updates 16 Aug 13:18:31 ntpd[48461]: ntpd: time set +32.207535 s ntpd: time set +32.207535s This can't be right. TIA, -Martin