From owner-freebsd-current@FreeBSD.ORG Sun Oct 19 09:08:11 2003 Return-Path: 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 A529A16A4B3 for ; Sun, 19 Oct 2003 09:08:11 -0700 (PDT) Received: from mta7.adelphia.net (mta7.adelphia.net [68.168.78.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACEC443F75 for ; Sun, 19 Oct 2003 09:08:10 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([68.68.113.33]) by mta7.adelphia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031019160813.UDTZ1452.mta7.adelphia.net@potentialtech.com>; Sun, 19 Oct 2003 12:08:13 -0400 Message-ID: <3F92B6E9.5030006@potentialtech.com> Date: Sun, 19 Oct 2003 12:08:09 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031005 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Guibert de Bruet References: <3F91E963.7080808@twcny.rr.com> <20031019113345.G54982@alpha.siliconlandmark.com> In-Reply-To: <20031019113345.G54982@alpha.siliconlandmark.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Tom Parquette cc: freebsd-current@freebsd.org Subject: Re: 5.1-CURRENT rebooting (multile systems) -- How to troubleshoot? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Oct 2003 16:08:11 -0000 Andre Guibert de Bruet wrote: > On Sat, 18 Oct 2003, Tom Parquette wrote: > >>My question is, if the system fails (I'm assuming these are panics) how >>do I get the machine to NOT automatically reboot so I can copy down the >>failure information? (Unless these are logged somewhere I have not >>found yet.) > > Try hooking up a serial console and logging a system run with "boot -v", > overnight. Make sure that you have all of the kernel debug options in > GENERIC in your kernel as they will provide insight that can help trace > the problem. Additionally, set your kernel up for debugging. This will allow you to get a great deal of information after a crash. This section of the developer's handbook will talk you through it: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html -- Bill Moran Potential Technologies http://www.potentialtech.com