From nobody Sun Apr 23 13:48:02 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 4Q48jL4hB4z45yDW for ; Sun, 23 Apr 2023 13:48:06 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 4Q48jL1fPRz3QGL for ; Sun, 23 Apr 2023 13:48:06 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-io1-xd2d.google.com with SMTP id ca18e2360f4ac-760f29073b4so106378239f.2 for ; Sun, 23 Apr 2023 06:48:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682257685; x=1684849685; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:sender :from:to:cc:subject:date:message-id:reply-to; bh=CsCKgDCkTc30M5ZRyumaccGbsm8TSHCjr8st8tjRn5I=; b=AuoQIFOHNNX/6KPrkIBBZ+581UEmzOWeyWvbXGCsujsBhG9erLKSkxV7p3BrF6KGsR uv94uFCQqzpCth6T77w4qy6V5V+pWRlweAV9mLoyLv2NH7aG+VMFA+QZ3hKzFJhBUnHH Pfh4S+8+feLeP5dLaGoJnYS7ZKlSkOdCbMu4N+ZDVmO3GfuaZCkxsPB4gJWEatIk9hti uDJqfGSNwgWdnRsTLFcopHFX+l9Y6qEPFUCbiM34jd02v6U/2YoLCt4aL92Tq5yhqOVy 6sh6DtoJuc4dlwsOJJXxwU1emux4zBvlLYb98IfNcVpErA4pGkeHPl/Dh3/yHgyaPch8 Ws8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682257685; x=1684849685; h=in-reply-to:content-transfer-encoding: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=CsCKgDCkTc30M5ZRyumaccGbsm8TSHCjr8st8tjRn5I=; b=SB3lnO3lRHCZH+O6pcroKMqD/2LWSSlX3cQICL3NvvmKq+/rAJAYCYFVN1ci6FMgWD ju9zImGrQMr3NT1eoFv8OzHd5UH/qz/SqD6FoTQHYOzPCkk4BDjr0NHG0huaqiYQT6pD IxSCXRrmv5lXcKnxkIJzedYQd8ZgmEmIETuXb4DN8+Efr7T+xhgyAYhJ/ee7fxNxRL3+ 90DO44t6wcq4mZqiYVUIIk0YOddfRfBfYl5kN8MgjYJqzyIlQGu9ue2H8w0n0PSr7jKp X0E+KATmsTOI4FOiEe10i6CYV8NrV0oB4wLekny0hITY2iK7yy27w4OeHPANxczrghVP fSMw== X-Gm-Message-State: AAQBX9dn2XIX5VdQmKXAj5ElaMawHhvySQ4EgKvuKMwqyLVKzYbY6gpx 5VhdZU5e9Jeqr9zNjwod2H37mt3HQ4g= X-Google-Smtp-Source: AKy350ZRB9X0670ku9uQzY6dVESVgLdp4XtIf+XdeHEv0sOfl/zKIwKL8DeYjjrZ8YxCwKmQJ5dZag== X-Received: by 2002:a05:6e02:109:b0:328:a112:f981 with SMTP id t9-20020a056e02010900b00328a112f981mr3325154ilm.4.1682257684908; Sun, 23 Apr 2023 06:48:04 -0700 (PDT) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id r20-20020a92c5b4000000b0032addae8ab1sm2474866ilt.69.2023.04.23.06.48.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 23 Apr 2023 06:48:04 -0700 (PDT) Date: Sun, 23 Apr 2023 09:48:02 -0400 From: Mark Johnston To: Mike Karels Cc: Peter Jeremy , current@freebsd.org Subject: Re: ntpd fails on recent -current/arm64 Message-ID: References: <33479649-394F-429D-A71B-12B3BC379149@karels.net> 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-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <33479649-394F-429D-A71B-12B3BC379149@karels.net> X-Rspamd-Queue-Id: 4Q48jL1fPRz3QGL 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 07:34:45AM -0500, Mike Karels wrote: > 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. I can reproduce the problem. A small example would still be useful, so that we can turn it into a regression test case.