From owner-freebsd-current@FreeBSD.ORG Sun Dec 19 20:17:20 2004 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 D69F516A4CE for ; Sun, 19 Dec 2004 20:17:20 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FA1543D54 for ; Sun, 19 Dec 2004 20:17:20 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iBJKHI8W099503; Sun, 19 Dec 2004 15:17:18 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iBJKH94J099499; Sun, 19 Dec 2004 15:17:18 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 19 Dec 2004 15:17:09 -0500 (EST) From: Andre Guibert de Bruet To: Sean McNeil In-Reply-To: <1103434515.1158.10.camel@server.mcneil.com> Message-ID: <20041219150157.O19917@alpha.siliconlandmark.com> References: <1103434515.1158.10.camel@server.mcneil.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: reboot without any info 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 Dec 2004 20:17:21 -0000 On Sat, 18 Dec 2004, Sean McNeil wrote: > This happens with a world/kernel and a portupgrade -frR totem built > Today: > > From rom a user account, I did a gdb `which totem` and then an r. This > caused a reboot. > > This brings up a couple of questions I have. > > 1) I do not get crash dumps. I have Your lack of any text at the console before the reboot indicates that a hardware problem (Overheating CPU, defective memory, overheating ata drives) is likely to be the cause of your woes. > dumpdev=/dev/ad4s1b > dumpon_enable="YES" > savecore_enable="YES" You forgot to specify dumpdir, the target directory for your core dump. I don't recall the existance of savecore_enable and it doesn't seem to be documented in /etc/defaults/rc.conf, either. Having unused options in rc.conf will, of course, not stop your dump from happening... > and in my kernel I have > > makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols > options KDB # Enable kernel debugger support. > options DDB # Support DDB. > options GDB # Support remote GDB. > > Are these options OK? Should I remove/add something to get it working? If you are suspecting bad behavior in your kernel, you probabaly should enable INVARIANTS and WITNESS as well. As I previously stated, at this point, you should probably start by examining the hardware FreeBSD is running on. In the future, I suggest that you paste the output of a `uname -a` with any bug reports as well as URL for the dmesg of the machine. It helps track things a bit better. :-) Regards, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >