Date: Sun, 26 May 2002 13:48:12 +0100 From: Dominic Marks <dominic_marks@btinternet.com> To: Ceri Davies <setantae@submonkey.net> Cc: hackers@FreeBSD.org Subject: Re: Another panic in -STABLE, yesterday's tree Message-ID: <20020526134812.A64544@host217-39-131-156.in-addr.btop> In-Reply-To: <20020526112641.GA396@submonkey.net>; from setantae@submonkey.net on Sun, May 26, 2002 at 12:26:41PM %2B0100 References: <20020526112641.GA396@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 26, 2002 at 12:26:41PM +0100, Ceri Davies wrote: > > I've had another kernel panic, this time from a cold boot (the machine had > been powered off overnight), with a new world and kernel built yesterday: > > FreeBSD rhadamanth.private.submonkey.net 4.6-PRERELEASE FreeBSD 4.6-PRERELEASE #0: Wed May 1 21:59:38 BST 2002 setantae@rhadamanth.private.submonkey.net:/usr/obj/usr/src/sys/RHADAMANTH i386 > > I've attached a backtrace - further information is available if someone > tells how to summon it from gdb (I won't delete vmcore this time...) I had this problem. To get good backtraces I do the following. I don't know how "good" this method is, but it works for me. After making your system with makeoptions="-g", add the following to /etc/rc.conf: savecore_flags="-N /usr/obj/usr/src/sys/GALLIUM/kernel.debug" Using the correct path for your kernel name. Then, in your crash dump directory (mine is /usr/crash) run gdb -k kernel.N vmcore.N and you should be able to get a good backtrace with symbols. I find doing it in other ways gets my the same kvm_read message as you have, which is no good. Someone (me) should update the part of the developers handbook because I found following its advice would not get my useful information. Thanks! -- Dominic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020526134812.A64544>