From owner-freebsd-current@FreeBSD.ORG Tue Jan 31 22:02:13 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6097A16A420; Tue, 31 Jan 2006 22:02:13 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 107AD43D48; Tue, 31 Jan 2006 22:02:13 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k0VM2Cl7025167; Tue, 31 Jan 2006 14:02:12 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k0VM2CMZ025166; Tue, 31 Jan 2006 14:02:12 -0800 (PST) (envelope-from sgk) Date: Tue, 31 Jan 2006 14:02:12 -0800 From: Steve Kargl To: Kris Kennaway Message-ID: <20060131220212.GA23528@troutmask.apl.washington.edu> References: <20060131212209.GA870@troutmask.apl.washington.edu> <20060131213332.GA15250@xor.obsecurity.org> <20060131213834.GA1080@troutmask.apl.washington.edu> <20060131214522.GA15709@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060131214522.GA15709@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, pjd@freebsd.org Subject: Re: panic: Memory modified after free X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2006 22:02:13 -0000 On Tue, Jan 31, 2006 at 04:45:22PM -0500, Kris Kennaway wrote: > On Tue, Jan 31, 2006 at 01:38:34PM -0800, Steve Kargl wrote: > > On Tue, Jan 31, 2006 at 04:33:32PM -0500, Kris Kennaway wrote: > > > On Tue, Jan 31, 2006 at 01:22:09PM -0800, Steve Kargl wrote: > > > > The system is a dual proc Tyan K8S Pro with 12 GB of memory. > > > > The kernel is UP. This was recorded by hand. I have the crash dump. > > > > > > > > Memory modified after free 0xffffff02505e0c00(504) val=deadc0dd @ > > > > 0xffffff02505e0cd0 > > > > > > > > panic: Most recently used by DEVFS1 > > > > > > Set up memguard to watch this malloc type in order to obtain useful > > > debugging. > > > > > > > OK, I've read the memguard manpage and it says to add > > > > vm.memguard.desc= > > > > to /boot/loader.conf. Where to I get info for what > > actually means? > > Look at the relevant MALLOC_DEFINE() in the source, it's the second > field (see malloc(9)). This should probably be clarified in the > memguard manpage. > Thanks. I've found the memory_type, and I rebuilding a kernel now with DEBUG_MEMGUARD. I can get the system to panic with 5 minutes, so I should have more information shortly. -- Steve