From owner-freebsd-hackers Thu Mar 22 5:30:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4D1C437B744 for ; Thu, 22 Mar 2001 05:30:20 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 22 Mar 2001 13:30:19 +0000 (GMT) Date: Thu, 22 Mar 2001 13:30:19 +0000 From: David Malone To: Dmitry Samersoff Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Help please (Server crash) Message-ID: <20010322133019.A93965@walton.maths.tcd.ie> References: <3AB9F10A.714B2433@wplus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB9F10A.714B2433@wplus.net>; from dms@wplus.net on Thu, Mar 22, 2001 at 03:33:14PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 22, 2001 at 03:33:14PM +0300, Dmitry Samersoff wrote: > Any ideas? With hangs like this using the debugger to find out what the kernel is doing is often the best bet. You'll need to compile the debugger into the kernel and then leave the server on a vty that doesn't have X running. When it hangs try breakin into the debugger (ctl-alt-esc) and get a trace (type trace). You may need to do this a few times to get an idea of what's going on. The kernel debugging section of the handbook has more details on this sort of thing. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message