From nobody Mon Oct 17 13:26:19 2022 X-Original-To: freebsd-hackers@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 4Mrd712G7Cz4fyBm for ; Mon, 17 Oct 2022 13:26:21 +0000 (UTC) (envelope-from jschauma@netmeister.org) Received: from panix.netmeister.org (panix.netmeister.org [166.84.7.99]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mrd703kYjz44Gn for ; Mon, 17 Oct 2022 13:26:20 +0000 (UTC) (envelope-from jschauma@netmeister.org) Received: by panix.netmeister.org (Postfix, from userid 1000) id 9BAFB85851; Mon, 17 Oct 2022 09:26:19 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=netmeister.org; s=2022; t=1666013179; bh=yKyWcaijA2wj8QdzcZ31nQHOF3GxIcy0MKVNLgmebhI=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=Lj+r9na/b743DjR8/xlQ9VO9frK8lWIbY941Y4Ed2ofQhlB43q/ru3fbighME0Uhe xA/1sceIGGHWqxLvmJhMYKF9QfXek7FNQBvbWgMP0dbQcNhpj82VBgKvM+zsXVGOVl F1iIcQQ7/9WSCyIYxxnP/vPt72uw2jI/IjLk+2/8NzesajKYcO0/74ga6eAL1G1QPV vRmntSeUR6c/i5optWmq9Y7KJm/BxEajc17MBm/TVXR+E9SmSgXomPHQoGkOBPI1cG VFse5VgBS39YQ9cTftDge+y5MwVl1k4YkOeByo2sn3OGAZrVLVTY8On4MHKP53NhsF XU6wFmco8lzag== Date: Mon, 17 Oct 2022 09:26:19 -0400 From: Jan Schaumann To: Michael Schuster Cc: FreeBSD Hackers Subject: Re: host unresponsive when setting time very far in the future Message-ID: Mail-Followup-To: Michael Schuster , FreeBSD Hackers References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Mrd703kYjz44Gn X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=netmeister.org header.s=2022 header.b="Lj+r9na/"; dmarc=pass (policy=quarantine) header.from=netmeister.org; spf=pass (mx1.freebsd.org: domain of jschauma@netmeister.org designates 166.84.7.99 as permitted sender) smtp.mailfrom=jschauma@netmeister.org X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[netmeister.org,quarantine]; R_DKIM_ALLOW(-0.20)[netmeister.org:s=2022]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2033, ipnet:166.84.0.0/16, country:US]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[netmeister.org:+]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Michael Schuster wrote: > On Mon, Oct 17, 2022, 04:10 Jan Schaumann wrote: > > I've observed that trying to set the date _very_ far > > in the future causes my FreeBSD AWS instance to become > > unresponsive and requiring a forced reboot to come > > back. (I don't see an actual kernel panic, however.) > > > > A few questions that come to mind: > - Which version of FreeBSD? > - which architecture (I know nothing of AWS, perhaps that's implied)? This was on AMI ami-00e91cb82b335d15f, from the official 13.0R announcement, amd64. > - have you tried this on a different platform (a VM or real HW)? No, I don't have those immediately available. But I just now tried on ami-0cf377776fddcf8ba, which is amd64 / 13.1R, where setting the date to 44093078356492800 succeeds. However, there the problem appears at 49282253052249598 epoch: # date -f "%s" 49282253052249598 Fri Dec 31 23:59:58 UTC 1561694399 # date -f "%s" 49282253052249599 Fri Dec 31 23:59:59 UTC 1561694399 [ reboots ~three seconds later ] I see a message in the logs that dhclient core dumped: Jan 1 00:00:14 freebsd kernel: pid 499 (dhclient), jid 0, uid 0: exited on signal 6 (core dumped) but that doesn't directly lead to the system rebooting. What's funny is is that after setting the date to 49282253052249598, it will continue to run just fine, even as the time advanced beyond the time at which it reboots when explicitly set. > Out of curiosity: why? :-) Exactly that: out of curiosity. :-) > One thing I'd do in a situation like this is display the numbers in hex, > that may give you a clue. In this case, I think the numbers point to the tm_year, as in both cases it's at the year end, it seems to me. -Jan