Date: Sun, 15 Apr 2007 01:20:07 GMT From: <bla@gericos.com> To: freebsd-bugs@FreeBSD.org Subject: RE: kern/111413: panic when nfsd running Message-ID: <200704150120.l3F1K76p051006@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: <bla@gericos.com> To: "'Kris Kennaway'" <kris@obsecurity.org> Cc: <freebsd-gnats-submit@FreeBSD.org> Subject: RE: kern/111413: panic when nfsd running Date: Sun, 15 Apr 2007 03:00:45 +0200 Hi Kris, The NFS server is totally KO. I cannot use it anymore, the server always crashes differently before launch any process at boot time. I'm certain it's a hardware problem. I will check it next week. You can close this case. Thanks. -----Message d'origine----- De=A0: Kris Kennaway [mailto:kris@obsecurity.org]=20 Envoy=E9=A0: mardi 10 avril 2007 05:49 =C0=A0: riton Cc=A0: freebsd-gnats-submit@FreeBSD.org Objet=A0: Re: kern/111413: panic when nfsd running 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): >=20 > FreeBSD/i386 (nfs01) (ttyd0) >=20 > login: Memory modified after free 0xcc0b0a00(508) val=3Ddead80de @ 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?200704150120.l3F1K76p051006>