Date: Mon, 26 Jun 2006 11:05:53 -0300 (ADT) From: "Marc G. Fournier" <scrappy@hub.org> To: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> Cc: freebsd-stable@freebsd.org Subject: Re: force panic of remote server ... possible? Message-ID: <20060626110502.L1114@ganymede.hub.org> In-Reply-To: <1151323574.80434.2.camel@buffy.york.ac.uk> References: <20060626085321.T1114@ganymede.hub.org> <1151323574.80434.2.camel@buffy.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 26 Jun 2006, 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? Unfortunately, no ... that's why we're moving to using HP servers, so that we have the proper tools in place to deal with things more effectively remotely ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060626110502.L1114>