From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by ur; Mon Jan  4 13:16:15 EST 2016
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46])
	by mailout.nyi.internal (Postfix) with ESMTP id 78624208C0
	for <9front@9front.org>; Mon,  4 Jan 2016 13:16:14 -0500 (EST)
Received: from web4 ([10.202.2.214])
  by compute6.internal (MEProxy); Mon, 04 Jan 2016 13:16:14 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=
	content-transfer-encoding:content-type:date:from:message-id
	:mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=+EO
	dBL4Uup+pHWMT7NeYrZax3w8=; b=dQovW9QRR7TTBQW9quz9E4fFe7yb5hLxcl7
	oye/8rTaT/tyoDyMF8mIOCKtBLR34KpcSsnU4SAZ5LB2m20njw7tBmiKrlk3Mfcg
	9FBOeswvFeVunLTJ/PTgJdvZD6qK//9P0bmOYgVmitizMsXSQ0A9zEeDAFSo36fR
	s1IGBUms=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
	messagingengine.com; h=content-transfer-encoding:content-type
	:date:from:message-id:mime-version:subject:to:x-sasl-enc
	:x-sasl-enc; s=smtpout; bh=+EOdBL4Uup+pHWMT7NeYrZax3w8=; b=qjpMb
	Ot/DgefPMK3I2py0QOXRc5O09k5oGt9ARdKMais7GEqbZh0flTz09qta+h2uMuum
	tvewiq3PPS/MfEeQTFinbMP0o2qj4i6kt6ogqpgPoVlgGFB2ZTt4qBazqZJjHIsX
	knoYKh7+dtpMuvuEB8PIydcLUXrw/S/eKaamRQ=
Received: by web4.nyi.internal (Postfix, from userid 99)
	id 49C83105C18; Mon,  4 Jan 2016 13:16:14 -0500 (EST)
Message-Id: <1451931374.2098653.482558226.11FAA1AE@webmail.messagingengine.com>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: shared strategy-scale method CSS controller
X-Sasl-Enc: 0nsbA17azl8OlF6zO94mLifoH6bUk7E94R6PKQ0eKn1v 1451931374
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@9front.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-42cc5299
Subject: todfix
Date: Mon, 04 Jan 2016 18:16:14 +0000

i have a 9front vm guest on a linux host. the host is suspended regularly. whenever it's resumed, the guest prints "todfix" and a number on the screen. if i understand the kernel code correctly, this is because the time jumped too much.

/sys/src/9/port/tod.c:210

it's a nuisance because it appears on the screen rather than through kprint, and it appears to be unnecessary; the guest has never failed to get the correct time after the host is resumed. the host has never been suspended more than about 12 hours, so it may not be much of a test. i've just paused the guest by a qemu feature, so if a longer test is wanted, i can keep it paused for a few days or a week or more. the guest's kernel is a little old (april) but i see port/tod.c:210 hasn't changed.up to the last iso.