Date: Tue, 10 Apr 2007 03:50:14 GMT From: Kris Kennaway <kris@obsecurity.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/111413: panic when nfsd running Message-ID: <200704100350.l3A3oEqW015891@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/111413; it has been noted by GNATS. From: Kris Kennaway <kris@obsecurity.org> To: riton <bla@gericos.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704100350.l3A3oEqW015891>