From owner-freebsd-bugs@FreeBSD.ORG Mon Dec 17 06:46:46 2007 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 881D016A417; Mon, 17 Dec 2007 06:46:46 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.freebsd.org (Postfix) with ESMTP id 68BEC13C45D; Mon, 17 Dec 2007 06:46:46 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.11.20060308/8.12.8) with ESMTP id lBH6MY6I018585; Sun, 16 Dec 2007 22:22:34 -0800 From: Kent Stewart To: yongari@freebsd.org Date: Sun, 16 Dec 2007 22:22:48 -0800 User-Agent: KMail/1.9.7 References: <200711271017.lARAHNAP000597@freefall.freebsd.org> In-Reply-To: <200711271017.lARAHNAP000597@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712162222.48925.kstewart@owt.com> Cc: freebsd-bugs@freebsd.org Subject: Re: kern/93893: [re] Boot panic from Netgear GA311 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2007 06:46:46 -0000 On Tuesday 27 November 2007, yongari@freebsd.org wrote: > Synopsis: [re] Boot panic from Netgear GA311 > > State-Changed-From-To: open->feedback > State-Changed-By: yongari > State-Changed-When: Tue Nov 27 10:16:46 UTC 2007 > State-Changed-Why: > The diagnostic code was commented out in newer code. > Is it still an issue on RELENG_6/RELENG_7? > > > Responsible-Changed-From-To: freebsd-bugs->yongari > Responsible-Changed-By: yongari > Responsible-Changed-When: Tue Nov 27 10:16:46 UTC 2007 > Responsible-Changed-Why: > Grab. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=93893 I haven't had one of these panics for a long time. I don't run RELENG_7. I had a loopback failure on an re device this morning on a system running RELENG_5 but all that happened was the NIC didn't work. I still had to reboot the system to get my internal network connected but it wasn't a panic.