From owner-freebsd-amd64@FreeBSD.ORG Mon Jul 17 20:44:05 2006 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 36CEE16A4DE for ; Mon, 17 Jul 2006 20:44:05 +0000 (UTC) (envelope-from sseekamp@risei.net) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0DE743D46 for ; Mon, 17 Jul 2006 20:44:04 +0000 (GMT) (envelope-from sseekamp@risei.net) Received: from 71-211-173-69.hlrn.qwest.net ([71.211.173.69] helo=monibeast.risei.net) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.51) id 1G2Zwh-000D95-RD for freebsd-amd64@freebsd.org; Mon, 17 Jul 2006 16:44:03 -0400 Received: from risei.net (localhost.risei.net [127.0.0.1]) by monibeast.risei.net (Postfix) with ESMTP id A0D891CC7A for ; Mon, 17 Jul 2006 14:44:02 -0600 (MDT) Received: from (SquirrelMail authenticated user sseekamp) by risei.net with HTTP; Mon, 17 Jul 2006 14:44:02 -0600 (MDT) X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 71.211.173.69 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: hobroblin Message-ID: <..1153169042.squirrel@risei.net> Date: Mon, 17 Jul 2006 14:44:02 -0600 (MDT) From: "Scott Seekamp" To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal Content-Transfer-Encoding: quoted-printable Subject: NVE Timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sseekamp@risei.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2006 20:44:05 -0000 I know the fix for this has been gone over a few times but does anyone have a confirmation of whether it will be included in 6.2 or some patch for 6.1? I really would like to get this error cleaned up but I want it official. Thanks Scott