From owner-freebsd-current@FreeBSD.ORG Mon Jul 26 21:51:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2B0B16A4CE; Mon, 26 Jul 2004 21:51:33 +0000 (GMT) Received: from lakermmtao06.cox.net (lakermmtao06.cox.net [68.230.240.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0647343D31; Mon, 26 Jul 2004 21:51:33 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao06.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040726215130.WFTZ9340.lakermmtao06.cox.net@dolphin.local.net>; Mon, 26 Jul 2004 17:51:30 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6QLpVHu001210; Mon, 26 Jul 2004 16:51:31 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6QLpVJs001209; Mon, 26 Jul 2004 16:51:31 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040726151035.GB1473@green.homeunix.org> Date: Mon, 26 Jul 2004 16:51:31 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Brian Fundakowski Feldman cc: freebsd-current@freebsd.org cc: Scott Long Subject: Re: [amd64] Instability worse than ever X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 21:51:33 -0000 On 26-Jul-2004 Brian Fundakowski Feldman wrote: > On Mon, Jul 26, 2004 at 06:58:23AM -0500, Conrad J. Sabatier wrote: >> >> OK, I've built a new kernel (after cvsup) with INVARIANTS and >> WITNESS enabled, and double-checked my serial debugging setup, >> however, it's just occurred to me that this probably isn't going to >> help very much in this particular situation, as I already had >> debug.debugger_on_panic enabled, and the system still just went >> directly to a reboot, bypassing the debugger altogether. > > Were you running X? It is recognized that the console is > "unavailable" when running X, and if no consoles are available, > debug.debugger_on_panic has no effect. Ah, OK. That would explain that. :-) -- Conrad J. Sabatier -- "In Unix veritas"