From owner-freebsd-current@FreeBSD.ORG Sun Oct 19 08:39:00 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 3952816A4B3 for ; Sun, 19 Oct 2003 08:39:00 -0700 (PDT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5745043F75 for ; Sun, 19 Oct 2003 08:38:59 -0700 (PDT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) h9JFcvZV071373; Sun, 19 Oct 2003 11:38:57 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)h9JFcuAb071370; Sun, 19 Oct 2003 11:38:57 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 19 Oct 2003 11:38:56 -0400 (EDT) From: Andre Guibert de Bruet To: Tom Parquette In-Reply-To: <3F91E963.7080808@twcny.rr.com> Message-ID: <20031019113345.G54982@alpha.siliconlandmark.com> References: <3F91E963.7080808@twcny.rr.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean 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 15:39:00 -0000 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. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >