From nobody Sun Apr 23 15:14:43 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Q4BdL41R3z463tx for ; Sun, 23 Apr 2023 15:14:46 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q4BdL3Xlvz3hB1 for ; Sun, 23 Apr 2023 15:14:46 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qt1-x82b.google.com with SMTP id d75a77b69052e-3ef6e8493ebso3096101cf.2 for ; Sun, 23 Apr 2023 08:14:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682262885; x=1684854885; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=C0GA8RZTlrR30oFVXBA2rLgd8yoOo+xVlgB3CB5aqcs=; b=OvjxNMBhUDpQ0/aTsPdpeJz6dyN/WkT6tpN8INq0PFugzFcZQe11SWJIXvH/0rWbd3 Hurq7qdE0CTZVWDc5nP+bzYyuOmHq35Gmn7NXbLHL3p7Dc3aOjAsINHRF10hpFFW4kLq FcHKWxYXRVARjP860naMyLsJLxzwfQuUYD2EdNUMnReCTMfcdoihpiYdGARIwF+V8I+/ 2lSlMiufF1DMDYknkcoJDae72OLZuT7z1fYZDNlpo4Kr7MNkcA1IEkQyN503rUazzL6J XyFaNjWuBiQvu1mFYNFYXOZy0zU8E+6t4LRDkowg2TvRI1r1moCRnr5IxlzEs5mn99Rt Nmug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682262885; x=1684854885; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=C0GA8RZTlrR30oFVXBA2rLgd8yoOo+xVlgB3CB5aqcs=; b=LQgQM3NNKAyMK32+Sb2OlVTElpoH98jliSJis/C8QJW3ojgTol4ef549uIXZwRN63J YZhbxEm/Ae92JEthJcZslxG6+8MXTNw8eSmDZGeiByHUmVotMuORaox7U8VPlE4nRLUv bKqo0Lmgxw7YQTOFGiO45GD1LV9r+jU6YuSQYCVnPOhg1tgMy0O7a/Xe6nkJm3a2bXrP buqhdhJTLtX276dWa1dlWda5y19YaUtZD3HBD801ViR4TwkDSJa/eIns05FgmehOA99I VgJalT6uAGc2kK7LYA2GjEkiDCuiYT9H7RdHc4Fs5nzYe/hC/vNmGWSIUm0z6bTS/Z9a g7nw== X-Gm-Message-State: AAQBX9dJwukPmPtiRZTY8G8nIdQdHt78ngQ9IpZyoIYAtxvburxuqbUn AcATDoGTMsqIWHanIavpBsrdLqgBCn0= X-Google-Smtp-Source: AKy350aA6RXL42RE+EMsIcMm6HY1KdsSWygc2KIsDhu8nhVEJ/yXZgxnz98CBBqgLHsnNUcORLzMug== X-Received: by 2002:ac8:7fd6:0:b0:3e4:d1c0:36a9 with SMTP id b22-20020ac87fd6000000b003e4d1c036a9mr15222247qtk.48.1682262885517; Sun, 23 Apr 2023 08:14:45 -0700 (PDT) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id ee27-20020a05620a801b00b0073b878e3f30sm2085244qkb.59.2023.04.23.08.14.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 23 Apr 2023 08:14:45 -0700 (PDT) Date: Sun, 23 Apr 2023 11:14:43 -0400 From: Mark Johnston To: Peter Jeremy Cc: current@freebsd.org Subject: Re: ntpd fails on recent -current/arm64 Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Q4BdL3Xlvz3hB1 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Sun, Apr 23, 2023 at 09:47:01PM +1000, Peter Jeremy wrote: > Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed, > some change in the kernel has made ntpd stop working on my arm64 test > box. (My amd64 test box is a couple of days behind so I'm not sure if > it's arm-specific). > > What I've identified so far: > * The problem is in the kernel, not userland. > * The impact seems to be limited to ntpd (in particular, ntpdate works). > * ntpd appears to be correctly exchanging NTP packets with peers. > * ntpd is not responding to "ntpq -p" queries > * ntp_gettime and ntp_adjtime both return TIME_ERROR to ntptime > > I've looked through the commits and, beyond much of netinet being > roto-tilled, I can't see anything obvious. > > Is anyone else seeing anything similar? Can anyone suggest where > to look next? This patch fixes the problem for me: https://reviews.freebsd.org/D39771