From owner-freebsd-arm@freebsd.org Tue Nov 14 22:03:57 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 37915DDF3F3 for ; Tue, 14 Nov 2017 22:03:57 +0000 (UTC) (envelope-from freebsd.asc@strcmp.org) Received: from onager.schwarzes.net (onager.schwarzes.net [IPv6:2a03:4000:8:2bb::5d22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C76CD71873; Tue, 14 Nov 2017 22:03:56 +0000 (UTC) (envelope-from freebsd.asc@strcmp.org) Received: from [172.30.250.35] (x4e330faa.dyn.telefonica.de [78.51.15.170]) (authenticated bits=0) by onager.schwarzes.net (8.15.2/8.15.2) with ESMTPA id vAEM3oJH085182; Tue, 14 Nov 2017 23:03:50 +0100 (CET) (envelope-from freebsd.asc@strcmp.org) From: Andreas Schwarz To: freebsd-arm@FreeBSD.org, ian@freebsd.org Mail-Reply-To: Andreas Schwarz Mail-Followup-To: freebsd-arm@FreeBSD.org Date: Tue, 14 Nov 2017 23:03:49 +0100 (CET) Message-ID: <4aff37249b6.70779c93@mail.schwarzes.net> In-Reply-To: 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> User-Agent: YAM/2.9p1 (MorphOS; PPC; rv:20140418r7798) Subject: Re: PINE64 - 12.0-CURRENT r324563 - ntpd can't keep time MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (onager.schwarzes.net [37.221.194.76]); Tue, 14 Nov 2017 23:03:50 +0100 (CET) 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: Tue, 14 Nov 2017 22:03:57 -0000 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? If you disable the ntpd, what time drift do you measure per day? > 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