From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 17 13:34:19 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 080C616A41F for ; Thu, 17 Nov 2005 13:34:19 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA20D43D75 for ; Thu, 17 Nov 2005 13:34:10 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1915096nzo for ; Thu, 17 Nov 2005 05:34:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=CYVZjf1yZgoDYT9oK6Ge7Vrgqc1vOJf9d4ThijHW5fx1YuvfDzYXD6W1w7WnKM3L3o9B8cJcEmysRvhcA0fjMBSy+FdomVEzXSsk8vod0D4NpN/gmjUYGE155Dxd3CaFSC7UM49oIH3hTGh7BThwRGJKIIDzhrQP4+ROCC7xteU= Received: by 10.36.177.11 with SMTP id z11mr7525518nze; Thu, 17 Nov 2005 05:34:09 -0800 (PST) Received: by 10.36.71.10 with HTTP; Thu, 17 Nov 2005 05:34:09 -0800 (PST) Message-ID: <28edec3c0511170534n14586426vd7cee0115e45b58c@mail.gmail.com> Date: Thu, 17 Nov 2005 21:34:09 +0800 From: "Mars G. Miro" To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: nasty amd64 date bug? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 13:34:19 -0000 Hiya list! Earlier today, one of my cow-orkers inadvertently did a: # date 190000000000 and his FreeBSD/amd64 box hung and dead on the water :-( I tried to reproduce it and can confirm that it only happens on FreeBSD/amd64, on 5.4R and in 6.0RC1 (6.0R might be affected). In i386 it just gives an 'incorrect date' message or something if you type in something not w/in 190300000000->203800000000 range. Also this requires root privs so not really something to panic. Any case, I wanted to break to debugger but ran out of time (mebe tomorrow when I'm back at work), or perhaps somebody else here who can risk crash-testing their amd64 boxen can try it. Thanks and FYI. cheers mars