From owner-freebsd-bugs@FreeBSD.ORG Tue Apr 10 03:50:15 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1762216A404 for ; Tue, 10 Apr 2007 03:50:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id B9CD813C46A for ; Tue, 10 Apr 2007 03:50:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l3A3oELZ015892 for ; Tue, 10 Apr 2007 03:50:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3A3oEqW015891; Tue, 10 Apr 2007 03:50:14 GMT (envelope-from gnats) Date: Tue, 10 Apr 2007 03:50:14 GMT Message-Id: <200704100350.l3A3oEqW015891@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: kern/111413: panic when nfsd running X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2007 03:50:15 -0000 The following reply was made to PR kern/111413; it has been noted by GNATS. From: Kris Kennaway To: riton Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/111413: panic when nfsd running Date: Mon, 9 Apr 2007 23:48:41 -0400 On Mon, Apr 09, 2007 at 02:50:15PM +0000, riton wrote: > When nfsd is running, here is the type of panic I have (not always the same): > > FreeBSD/i386 (nfs01) (ttyd0) > > login: Memory modified after free 0xcc0b0a00(508) val=dead80de @ 0xcc0b0b7c > panic: Most recently used by vnodemarker You will need to configure DEBUG_MEMGUARD to watch this malloc type. Unfortunately this requires a tiny change to the source so it is not completely trivial, but see memguard(9). Once you have done this, you will hopefully get a different panic when the memory is first accessed after it was freed, and we can proceed from there. Kris