From owner-freebsd-current Fri May 24 17:30:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from drone2.qsi.net.nz (drone2-svc-skyt.qsi.net.nz [202.89.128.2]) by hub.freebsd.org (Postfix) with SMTP id 69E3937B406 for ; Fri, 24 May 2002 17:30:51 -0700 (PDT) Received: (qmail 92229 invoked by uid 0); 25 May 2002 00:30:48 -0000 Received: from unknown (HELO COMPUTER.ijs.co.nz) ([202.89.142.240]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 25 May 2002 00:30:48 -0000 Message-Id: <5.1.1.2.2.20020525120838.03356390@202.89.128.27> X-Sender: research@202.89.128.27 X-Mailer: QUALCOMM Windows Eudora Version 5.1.1.3 (Beta) Date: Sat, 25 May 2002 12:30:57 +1200 To: freebsd-current@freebsd.org From: Craig Carey Subject: Re: reading kernel dump - post gcc 3.1 Cc: "Georg-W. Koltermann" In-Reply-To: <1022244779.4521.96.camel@hunter.muc.macsch.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 02\05\24 14:52 +0200 Friday, Georg-W. Koltermann wrote: >Hi, > >I got a couple of kernel panics recently, some of them "buffer not >locked". I would like to know how I can get more information out of the >dump. > >The system's gdb does not like the dump format any more, see also >bin/38236. There is an advertised workaround in that pr of using gdb52, >but I couldn't get that to work ("not a core dump: File format not >recognized"). > >Am I missing something? How do you guys read your dumps? > There are online articles on how to get and read kernel panic dumps, at these webpages. Also I copy parts views the articles. http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html?page=2 System Panics, Part 1: Preparing for the Worst (21 March 2002), by Mr. M. Lucas Add: options DDB makeoptions DEBUG=-g to config file. A large enough swap file is needed for the dump. Specify in /etc/rc.conf: dumpdev="/dev/ad0s4b", the dumpdir may be specified to be /var/crash. Read savecore(8). http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html?page=2 System Panics, Part 2: Recovering and Debugging (4 April 2002) savecore(8) should copy a dump of the crashed kernel to /var/crash and created files kernel.0 and vmcore.0. gdb -k kernel.0 vmcore.0 __ Craig Carey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message