From owner-freebsd-stable@FreeBSD.ORG Mon Oct 27 16:03:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E1971065675 for ; Mon, 27 Oct 2008 16:03:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 877908FC0C for ; Mon, 27 Oct 2008 16:03:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id m9RG2Y1c012952; Mon, 27 Oct 2008 12:02:56 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Jo Rhett Date: Mon, 27 Oct 2008 11:52:44 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810271152.46716.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Mon, 27 Oct 2008 12:02:56 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8508/Mon Oct 27 09:02:44 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-stable Stable Subject: Re: 6.4 RC1 locks up solid on first reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2008 16:03:04 -0000 On Friday 24 October 2008 03:05:32 pm Jo Rhett wrote: > John, is this perhaps the problem seen with 7.0, discussed here? > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-05/msg00437.html It is related, but that fix is already in 6.4. -- John Baldwin