From owner-freebsd-stable@FreeBSD.ORG Mon Jun 26 18:43:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A55B916A526 for ; Mon, 26 Jun 2006 18:43:17 +0000 (UTC) (envelope-from emaste@phaedrus.sandvine.ca) Received: from gw.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 599C64515B for ; Mon, 26 Jun 2006 14:52:41 +0000 (GMT) (envelope-from emaste@phaedrus.sandvine.ca) Received: from mailserver.sandvine.com ([192.168.1.10]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Jun 2006 10:52:39 -0400 Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by mailserver.sandvine.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Jun 2006 10:52:38 -0400 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 12627) id 4461811607; Mon, 26 Jun 2006 10:52:38 -0400 (EDT) Date: Mon, 26 Jun 2006 10:52:38 -0400 From: Ed Maste Message-ID: <20060626145238.GA22081@sandvine.com> References: <20060626085321.T1114@ganymede.hub.org> <1151323574.80434.2.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1151323574.80434.2.camel@buffy.york.ac.uk> User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 26 Jun 2006 14:52:38.0464 (UTC) FILETIME=[2AF24C00:01C69930] Cc: freebsd-stable@freebsd.org Subject: Re: force panic of remote server ... possible? 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, 26 Jun 2006 18:43:17 -0000 On Mon, Jun 26, 2006 at 01:06:14PM +0100, Gavin Atkinson wrote: > On Mon, 2006-06-26 at 08:55 -0300, Marc G. Fournier wrote: > > For the server that I'm fighting with right now, where Dmitry pointed out > > that it looks like a deadlock issue ... I have dumpdev/savecore enabled, > > is there some way of forcing it to panic when I know I actually have the > > deadlock, so that it will dump a core? > > You cen enter the debugger by setting the (badly names) debug.kdb.enter > sysctl to 1, although I can't guarantee that'll trigger a dump and > reboot. Do you have a serial console? >From some of your other messages, I believe this is a remote machine? Unless you can access an attached keyboard, or have a serial console, debug.kdb.enter will leave the machine sitting in ddb with no way to get out. Also, if you have a PS/2 keyboard (that is, one handled by the atkbd(4) driver) ddb will not accept any input on 6.1 or HEAD. (There is some discussion of this issue on the freebsd-current list.) Before using ddb on a remote machine I would suggest testing it out with the same release locally. For your original question -- I'm not sure which release it first appeared in (and it may be only in -CURRENT), but if it exists you can use: $ sysctl -d debug.kdb.panic debug.kdb.panic: set to panic the kernel -ed