From owner-freebsd-stable@FreeBSD.ORG Sat Dec 30 18:29:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3D29216A407 for ; Sat, 30 Dec 2006 18:29:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1319D13C428 for ; Sat, 30 Dec 2006 18:29:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id A72524761F; Sat, 30 Dec 2006 13:29:38 -0500 (EST) Date: Sat, 30 Dec 2006 18:29:38 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Karol Kwiatkowski In-Reply-To: <4596AF32.2060205@orchid.homeunix.org> Message-ID: <20061230182714.O18740@fledge.watson.org> References: <20061230035722.L39715@thebighonker.lerctr.org> <20061230151933.P18740@fledge.watson.org> <20061230093730.I47579@thebighonker.lerctr.org> <20061230160353.K18740@fledge.watson.org> <45969487.1020806@orchid.homeunix.org> <20061230170358.K50974@fledge.watson.org> <4596AF32.2060205@orchid.homeunix.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: debugging kernel options (was: Re: 6.2-PRE: Fatal Trap?) 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: Sat, 30 Dec 2006 18:29:39 -0000 On Sat, 30 Dec 2006, Karol Kwiatkowski wrote: > Robert Watson wrote: >>> P.S. out of curiosity - now that I have configured kernel with DDB and >>> KDB options, is there any performance penalty of running such kernel? >> >> No, it shouldn't really have any effect on performance. The one thing to >> watch out for is that your system will no longer reboot automatically on a >> panic, as it will drop to the debugger, by default. You can change this by >> setting debug.debugger_on_panic to 0, in which case you will likely want to >> set debug.trace_on_panic to 1 so it prints a stack trace before rebooting >> (which is often sufficient, combined with the trap frame and panic message >> to debug the problem). >> >> Right now these are sysctls, not tunables, but you can change the default >> using options KDB_UNATTENDED (which flips the default to not entering the >> debugger and rebooting) and options KDB_TRACE (which causes a trace to be >> printed on panic by default). Probably they should also be tunables so >> that loader.conf entries will work. > > Great explanation, thank you. I turned on debugging on my desktop computer > which, apart from normal every day use, is 'testing' STABLE by running it :) > I'm perfectly fine with the defaults, at least for now. BTW, if you're running X on your desktop, be aware that it's X that does all the video mode management. If your box enters the debugger while in X, the debugger doesn't know how to switch back to text mode (and X isn't running, obviously), so while you'll be talking to the debugger, the chances you'll see anything comprehensible are actually quite low. For this reason, I normally also use a serial console when debugging desktop boxes: I can always plug my notebook in with a serial cable to see why it's entered the debugger. Robert N M Watson Computer Laboratory University of Cambridge