Date: Mon, 25 Nov 2019 10:01:58 -0800 From: Cy Schubert <Cy.Schubert@cschubert.com> To: freebsd-current@freebsd.org, =?ISO-8859-1?Q?Vin=EDcius_Zavam?= <egypcio@googlemail.com> Subject: Re: Fwd: [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: 0x41: Clock Unsynchronized) Message-ID: <934EBF76-8CEF-423D-A0A9-B66407FB66F6@cschubert.com> In-Reply-To: <CA%2BKr6DPmvgqSyhmwgnig6bAYYVPUe9G=2YCK4oizaE03BUe5_A@mail.gmail.com> References: <CA%2BKr6DPoi0Dxfrofprh3nwpc_H1CNmfxR_NmxwDmVQjCupaexQ@mail.gmail.com> <CA%2BKr6DPmvgqSyhmwgnig6bAYYVPUe9G=2YCK4oizaE03BUe5_A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On November 25, 2019 1:05:34 AM PST, "VinÃcius Zavam" <egypcio@googlemail.com> wrote: >as this one also hits HEAD, I am forwarding this email to current@. > >---------- Forwarded message --------- >Von: VinÃcius Zavam <egypcio@> >Date: Do., 21. Nov. 2019 um 12:22 Uhr >Subject: [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does >not >match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: >0x41: Clock Unsynchronized) >To: <freebsd-stable@> > > >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242137 >_______________________________________________ >freebsd-current@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscribe@freebsd.org" I don't have access to bugzilla through this phone (I haven't memorized my gibberish password) so I'll answer here for now and update the PR when I get to a real keyboard with internet access in a few hours. I suspect your clock is drifting enough over that it's stepping the clock and starting over. What are the contents of /var/db/ntpd.drift on your affected and unaffected machines in the PR? I'd also be interested in seeing ntpq -p outputs side-by-side. -- Pardon the typos and autocorrect, small keyboard in use. Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://www.FreeBSD.org The need of the many outweighs the greed of the few. Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-current@freebsd.org Mon Nov 25 19:09:57 2019 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C77281B6B50 for <freebsd-current@mailman.nyi.freebsd.org>; Mon, 25 Nov 2019 19:09:57 +0000 (UTC) (envelope-from SRS0Æ/G=ZR=quip.cz 0.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 47MGnJ74sCz3KPn for <freebsd-current@freebsd.org>; Mon, 25 Nov 2019 19:09:56 +0000 (UTC) (envelope-from SRS0Æ/G=ZR=quip.cz 0.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 6300028416; Mon, 25 Nov 2019 20:09:54 +0100 (CET) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9032428411; Mon, 25 Nov 2019 20:09:53 +0100 (CET) Subject: Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL To: Ruslan Garipov <ruslanngaripov@gmail.com>, freebsd-current@freebsd.org References: <5596338e-134c-9849-de9e-710d3106687f@gmail.com> <bf490832-9433-f5a4-afe2-2463652f453b@quip.cz> <a03e4c56-1c20-9b68-2a27-b3f6f91da18b@gmail.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <41b921c4-568f-5bd1-ae0f-1d85d750a8c7@quip.cz> Date: Mon, 25 Nov 2019 20:09:53 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <a03e4c56-1c20-9b68-2a27-b3f6f91da18b@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47MGnJ74sCz3KPn X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0Æ/G=ZR=quip.cz 0.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0Æ/G=ZR=quip.cz 0.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.07 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.89)[ip: (0.39), ipnet: 94.124.104.0/21(0.20), asn: 42000(3.74), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.988,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(0.99)[0.994,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0Æ/G=ZR=quip.cz 0.fbsd@elsa.codelab.cz]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0Æ/G=ZR=quip.cz 0.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 25 Nov 2019 19:09:57 -0000 Ruslan Garipov wrote on 2019/11/25 19:26: [...] >> I didn't tried this with current but I am using it with stable (11.3 at >> this time). Building on Xeon E3-1240v3 and installing on many different >> machines. Some of them are 10+ years old AMD Opteron, some Xeon E5649, >> some 10 years old Intel Pentium. >> So at least it worked in the past (11.3 amd64). Did you use this >> workflow in the past / did it work? > No, unfortunately I didn't. Always built world/kernel on target host. > >> I remember some issue in the past which was (accidentally?) fixed by >> running "make buildworld && make builkernel && make installkernel && >> make installworld" on the build host (to some different DESTDIR) and >> then "make installkernel && make installworld" on the target host (build >> machine is shared via NFS) > Therefore, this trick somehow "fixes" /usr/obj shared on the build > machine? I'll try this later. Thanks! Yes, I think so. But I am not a developer nor I know much about how build process works. Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?934EBF76-8CEF-423D-A0A9-B66407FB66F6>