From nobody Sun Apr 23 12:34:45 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 4Q474r6Bqwz45Mt9 for ; Sun, 23 Apr 2023 12:34:52 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q474r4dZhz4HqS for ; Sun, 23 Apr 2023 12:34:52 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTP id 33NCYkgm013220; Sun, 23 Apr 2023 07:34:46 -0500 (CDT) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1682253286; bh=cZx/0xFbmbov91lf0pVlYYzHByErIRikCECmXGTJNwU=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=qNckYW6f0PD1x6dNxO3w111yJTLsfTmlRnFCXb5ZRCVIhLkNXQ2tipfyKPsMnAYC5 VcKvsRR6QjUPD91qq6PkszoMK/oVKhfEhZ2LUsdigtMXzue4c6FjiMaP0WjmrE/7NN AXGUehR8GVaWsMMLjjwVprhny8Xs015UD8FvLa6z2zyJfvwJippTpsPao1u9KEHth3 1SuFquq83lZvnRcJwn5wi6Fi7BPFSJwXTKXsRfhDN6tUmjijySZjM3tDkamX8r4jVN 0zOufLd1t/9aP2aDJJqroybn9v63XzdrCy/5ePC9sxiR728765aPb7lYBqV9kXHUWU qIZpTy5oztkMA== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id kgs1C+YlRWSiMwAAs/W3XQ (envelope-from ); Sun, 23 Apr 2023 07:34:46 -0500 From: Mike Karels To: Peter Jeremy Cc: current@freebsd.org Subject: Re: ntpd fails on recent -current/arm64 Date: Sun, 23 Apr 2023 07:34:45 -0500 X-Mailer: MailMate (1.14r5964) Message-ID: <33479649-394F-429D-A71B-12B3BC379149@karels.net> In-Reply-To: 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=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4Q474r4dZhz4HqS X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 23 Apr 2023, at 6:47, 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 updated an amd64 system yesterday, and it is broken too. > I've looked through the commits and, beyond much of netinet being > roto-tilled, I can't see anything obvious. The netinet changes seem likely to be the culprit. ntpd seems to be receiving the requests but isn’t responding. Trivial testing indicates that named is working, so UDP isn’t completely broken. > Is anyone else seeing anything similar? Can anyone suggest where > to look next? Mark may have an idea. Finding a simpler example would be helpful, but I’m not sure what we’re looking for. Mike