From owner-freebsd-questions@FreeBSD.ORG Sun Apr 10 17:45:32 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31C8116A4CE for ; Sun, 10 Apr 2005 17:45:32 +0000 (GMT) Received: from pat.uio.no (pat.uio.no [129.240.130.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45A2A43D2D for ; Sun, 10 Apr 2005 17:45:31 +0000 (GMT) (envelope-from heikkis@matnat.uio.no) Received: from mail-mx6.uio.no ([129.240.10.47]) by pat.uio.no with esmtp (Exim 4.43) id 1DKgUz-0007Ev-PW for freebsd-questions@freebsd.org; Sun, 10 Apr 2005 19:45:29 +0200 Received: from ves-dhcp190.studby.uio.no ([129.240.102.220] helo=b-ko.wired) by mail-mx6.uio.no with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1DKgUw-0008EK-SS for freebsd-questions@freebsd.org; Sun, 10 Apr 2005 19:45:26 +0200 Date: Sun, 10 Apr 2005 19:43:49 +0200 From: heikki soerum To: freebsd-questions@freebsd.org Message-Id: <20050410194349.388fbecb.heikkis@matnat.uio.no> X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-UiO-Spam-info: not spam, SpamAssassin (score=-6.511, required 12, autolearn=disabled, ALL_TRUSTED -2.82, AWL 1.31, UIO_MAIL_IS_INTERNAL -5.00) Subject: debuging options in FBSD-5.x X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2005 17:45:32 -0000 Hello every fellow freebsd user. I've been browsing the handbook and I can't quite catch how to make an fully debugging 5.x kernel so that whenever I need to post an pr/bug it actuallty contains useful information for the bughunters. is the makeoptions DEBUG=-g enough? Or should the kernel be configured with addition options so an memory dump etc. would be available? What kernel-tunings and config changes are needed to be completely sure to catch an kernel crash and record useful information? At the moment I'm running an Freebsd CVS STABLE-5.4 from 08.april.2005 At the moment I have an very nasty nfs vs ata-sleep/idle kernel panic that reared it's ugly head after upgrading to STABLE-5 from RELEASE-5.2.1. I'l post more about this one after I've gotten an kernel running with all debuging enabled. After all, it's practically useless to post an PR without any debugging available. PS. As I'm not an regular subscriber to the mailinglist, I would like to get any replies cc'ed to me personally. Heikki Soerum. -- "Throughout history it has been the inaction of those who could have acted, the indifference of those who should have known better, the silence of the voice of justice when it mattered most, that has made it possible for evil to triumph." - Haile Selassie