Date: Wed, 16 May 2007 13:19:36 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Andrew Edwards <aedwards@sandvine.com> Cc: freebsd-fs@freebsd.org, freebsd-performance@freebsd.org Subject: Re: Ufs dead-locks on freebsd 6.2 Message-ID: <20070516171936.GA74455@xor.obsecurity.org> In-Reply-To: <5230D3C40B842D4F9FB3CD368021BEF72F08F3@exchange-2.sandvine.com> References: <20070516163305.GA73495@xor.obsecurity.org> <5230D3C40B842D4F9FB3CD368021BEF72F08F3@exchange-2.sandvine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 16, 2007 at 01:16:27PM -0400, Andrew Edwards wrote: > Here's the backtrace from the last crash along with the output from show > alllocks when the system was deadlocked. I have been running > 6.2-release and compliled with makeoptions debug=-g, invariants, > invariant_support and witness. I will update to 6-STABLE add > diagnositc, debug_locks and debug_vfs_locks as per the handbook > recommendation and retry. > > Yes, when the system was un-usable I was still able to ping it. I have > the serial console setup as the default console so I can remotely access > the box and break into the debugger etc. > > (kgdb) bt > #0 doadump () at pcpu.h:165 > #1 0xc059b480 in boot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:409 > #2 0xc059b795 in panic (fmt=0xc0787b04 "Most recently used by %s\n") > at /usr/src/sys/kern/kern_shutdown.c:565 That's a memory use-after-free. Check the DEBUG_MEMGUARD infrastructure for debugging of this. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070516171936.GA74455>