From owner-freebsd-net@FreeBSD.ORG Sat Apr 26 13:09:08 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 758) id 34B5F1065677; Sat, 26 Apr 2008 13:09:08 +0000 (UTC) Date: Sat, 26 Apr 2008 13:09:08 +0000 From: Kris Kennaway To: misha saf Message-ID: <20080426130908.GE47671@hub.freebsd.org> References: <200804250720.m3P7K3Jk019605@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200804250720.m3P7K3Jk019605@freefall.freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@FreeBSD.org Subject: Re: misc/123066: kernel trap with ipsec X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2008 13:09:08 -0000 On Fri, Apr 25, 2008 at 07:20:03AM +0000, misha saf wrote: > The following reply was made to PR kern/123066; it has been noted by GNATS. > > From: misha saf > To: Kris Kennaway > Cc: > Subject: Re: misc/123066: kernel trap with ipsec > Date: Fri, 25 Apr 2008 10:59:33 +0400 > > * Kris Kennaway [Fri, 25 Apr 2008 05:46:54 +0000]: > > On Fri, Apr 25, 2008 at 04:13:40AM +0000, Mihail wrote: > > > > > (kgdb) backtrace > > > #0 doadump () at pcpu.h:195 > > > #1 0xc075df57 in boot (howto=260) at > > /usr/src/sys/kern/kern_shutdown.c:409 > > > #2 0xc075e219 in panic (fmt=Variable "fmt" is not available. > > > ) at /usr/src/sys/kern/kern_shutdown.c:563 > > > #3 0xc0a9766c in trap_fatal (frame=0xc884e934, eva=3621180904) > > > at /usr/src/sys/i386/i386/trap.c:899 > > > #4 0xc0a978f0 in trap_pfault (frame=0xc884e934, usermode=0, > > eva=3621180904) > > > at /usr/src/sys/i386/i386/trap.c:812 > > > #5 0xc0a9829c in trap (frame=0xc884e934) at > > /usr/src/sys/i386/i386/trap.c:490 > > > #6 0xc0a7e21b in calltrap () at > > /usr/src/sys/i386/i386/exception.s:139 > > > #7 0xc0a952f6 in generic_bcopy () at > > /usr/src/sys/i386/i386/support.s:498 > > > Previous frame inner to this frame (corrupt stack?) > > > > Unfortunately we need the rest of the stack. Can you either try to > > reproduce with DDB in the kernel and obtain a stack trace from there, > > or if this is not possible then try recompiling the kernel with -O > > instead of -O2 which tends to produce better stack traces. > > > > Kris > That's all needed info ? No, stack frames 8 and beyond contained the important parts of the stack trace, but were not displayed by gdb. What we need is what I explained above. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe