From owner-freebsd-current Tue Nov 5 7:35:51 2002 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 40AA037B404 for ; Tue, 5 Nov 2002 07:35:50 -0800 (PST) Received: from mail.speakeasy.net (mail17.speakeasy.net [216.254.0.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9A6443E4A for ; Tue, 5 Nov 2002 07:35:49 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 21853 invoked from network); 5 Nov 2002 15:35:52 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail17.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 5 Nov 2002 15:35:52 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gA5FZkn5048678; Tue, 5 Nov 2002 10:35:48 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15815.56296.463941.374808@grasshopper.cs.duke.edu> Date: Tue, 05 Nov 2002 10:35:48 -0500 (EST) From: John Baldwin To: Andrew Gallatin Subject: Re: Why is my -current system Hard Locking? Cc: current@FreeBSD.ORG, "Joel M. Baldwin" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 05-Nov-2002 Andrew Gallatin wrote: > > Joel M. Baldwin writes: > > <...> > > don't think this is related to the X FP problem ( although I am > > running X11 ). There have been many times when I'd walk in the > <...> > > options DDB #Enable the kernel debugger > <...> > > Its likley you are panic'ing in X, and the system is waiting at the > ddb prompt. But you can't see it or do anything, since X has control > of the graphics and kbd, so it looks like the machine is frozen. > > Try adding options DDB_UNATTENDED to your config. Or just do > sysctl debug.debugger_on_panic=0 > > Both of these have the same effect: they will prevent ddb from stopping > the panic. Make sure you have a dump device setup to capture a > crashdump. DDB is smart enough (if you are using sc(4)) to notice that the display is in graphics mode and won't drop into a debugger prompt if you panic. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message