From owner-freebsd-arm@freebsd.org Thu Nov 16 09:49:48 2017 Return-Path: Delivered-To: freebsd-arm@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 6AD2ADD79BB for ; Thu, 16 Nov 2017 09:49:48 +0000 (UTC) (envelope-from hlh@restart.be) Received: from tignes.restart.be (tignes.restart.be [5.135.182.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tignes.restart.be", Issuer "CA master" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 05A24742EB for ; Thu, 16 Nov 2017 09:49:47 +0000 (UTC) (envelope-from hlh@restart.be) X-Comment: SPF check N/A for local connections - client-ip=192.168.25.127; helo=restart.be; envelope-from=hlh@restart.be; receiver=freebsd-arm@freebsd.org DKIM-Filter: OpenDKIM Filter v2.10.3 tignes.restart.be 3ycxKv1LGCzrtY Received: from restart.be (norquay.tunnel.bel [192.168.25.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.restart.be", Issuer "CA master" (verified OK)) by tignes.restart.be (Postfix) with ESMTPS id 3ycxKv1LGCzrtY for ; Thu, 16 Nov 2017 10:49:38 +0100 (CET) Received: from chamonix.restart.bel (chamonix.restart.bel [192.168.24.9]) (authenticated bits=0) by restart.be (8.15.2/8.15.2) with ESMTPSA id vAG9nbTx091956 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 16 Nov 2017 10:49:38 +0100 (CET) (envelope-from hlh@restart.be) Subject: Re: PINE64 - 12.0-CURRENT r324563 - ntpd can't keep time To: freebsd-arm@FreeBSD.org References: <4BF75B1E-318C-414A-B5D4-4BA7D6578316@dsl-only.net> <1509029871.56824.49.camel@freebsd.org> <4af740148ca.47a474e3@mail.schwarzes.net> <04b67007-a95a-9e40-28b4-764adf8b2ded@restart.be> <4aff37249b6.70779c93@mail.schwarzes.net> From: Henri Hennebert Message-ID: <3e6a8ce3-1b12-1557-ad0c-7b2259ced263@restart.be> Date: Thu, 16 Nov 2017 10:49:37 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <4aff37249b6.70779c93@mail.schwarzes.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 09:49:48 -0000 On 11/14/2017 23:03, Andreas Schwarz wrote: > On 14.11.17, Henri Hennebert wrote: >> On 11/13/2017 21:03, Mark Millard wrote: >>> >>> So it looks like you are getting bad times from at >>> least 2 servers. Note that the other servers seem >>> fine as far as your e-mailed material goes. >> >> I believe that the clock of the Pine64+ is going too fast and that the 2 >> servers where polled and so show this offset/jitter. In an other >> occurrence of this problem, if I wait long enough, all servers display >> huge offset. > > But they step not simultaneous to this offset (which is ~300s), why should some > servers have such offset and others not?. > > Can you provide your "ntpq -c rl" output? [root@norquay norquay]# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== 0.freebsd.pool. .POOL. 16 p - 64 0 0.000 0.000 0.000 94.143.184.140 .GPS. 1 u 51 128 17 16.202 -1.216 95656.2 178.32.44.208 ( 162.23.41.10 2 u 128 128 17 15.085 -178951 178957. ssh2.ulyssis.st 193.79.237.14 2 u 124 128 17 14.255 1.174 67639.2 ntp.kennisdelen 193.190.230.66 2 u 3 128 37 14.844 1.526 95655.9 hades.boxed-it. 193.67.79.202 2 u 60 128 17 12.179 1.281 146117. s01.be.it2go.eu 193.190.230.66 2 u 54 128 17 27.489 2.413 113181. 213.189.188.3.i 193.190.230.65 2 u 54 128 17 15.965 -178956 163366. ntp.katho.be 193.190.230.66 2 u 7 128 17 16.901 -2.730 95653.6 ntp.gillam-fei. 172.16.200.253 2 u 65 128 17 21.549 -178955 178957. *ntp.cybertu.be 193.190.230.65 2 u 10 128 3 15.199 -178955 0.134 [root@norquay norquay]# ntpq -c rl associd=0 status=0613 leap_none, sync_ntp, 1 event, spike_detect, version="ntpd 4.2.8p10-a (1)", processor="arm64", system="FreeBSD/12.0-CURRENT", leap=00, stratum=3, precision=-21, rootdelay=19.914, rootdisp=179188.957, refid=51.255.138.215, reftime=ddb7da3d.1efde957 Thu, Nov 16 2017 10:34:53.121, clock=ddb7da85.9f27db8d Thu, Nov 16 2017 10:36:05.621, peer=30993, tc=7, mintc=3, offset=1.497713, frequency=28.955, sys_jitter=0.000000, clk_jitter=1.380, clk_wander=0.097, tai=37, leapsec=201701010000, expire=201712280000 > > If you disable the ntpd, what time drift do you measure per day? > With nrpd disabled, while running svn update on /usr/ports, after 1/2 hour the clock was 6 minutes in the future. >> In a old version of Freebsd12, when dev.cpu.0.freq was accessible, the >> problem appear when I force the frequency to 1200. > > > The dev.cpu.0.freq is already there in head/current. > > root@pinelot:~ # sysctl dev.cpu.0 > dev.cpu.0.freq_levels: 1200/-1 1008/-1 816/-1 648/-1 408/-1 > dev.cpu.0.freq: 408 > dev.cpu.0.%parent: cpulist0 > dev.cpu.0.%pnpinfo: name=cpu@0 compat=arm,cortex-a53 > dev.cpu.0.%location: > dev.cpu.0.%driver: cpu > dev.cpu.0.%desc: Open Firmware CPU > > root@pinelot:~ # uname -v > FreeBSD 12.0-CURRENT #0 r325561: Thu Nov 9 11:24:55 CET 2017 root@pinelot.schwarzes.net:/usr/obj/usr/src/arm64.aarch64/sys/PINE64-ASC > > > -asc > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >