Date: Wed, 4 Feb 2004 14:38:08 +0100 From: Frode Nordahl <frode@nordahl.net> To: "Andrew P. Lentvorski, Jr." <bsder@allcaps.org> Cc: freebsd-current@freebsd.org Subject: Re: rpc.lockd(8) seg faults on 5.2-RELEASE Message-ID: <5E1365DC-5717-11D8-B0FA-000A95A9A574@nordahl.net> In-Reply-To: <20040203140450.T36001@mail.allcaps.org> References: <3DC16400-517B-11D8-9CB2-0005028F6AEB@TrueStep.com> <B6959364-5240-11D8-91E0-000A95A9A574@nordahl.net> <68FC202A-525D-11D8-B122-000A95A9A574@nordahl.net> <20040129135653.H21660@mail.allcaps.org> <E0D094EB-562D-11D8-95DC-000A95A9A574@nordahl.net> <20040203140450.T36001@mail.allcaps.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 3, 2004, at 23:12, Andrew P. Lentvorski, Jr. wrote: > On Tue, 3 Feb 2004, Frode Nordahl wrote: > >> Since it dies on bcmp, it seems like a null lock gets into the list >> for >> some reason. > > Turn on the debug log and uncomment DUMP_FILELOCK_VERBOSE (or just the > filehandle dump code in dump_filelock). One of those locks should > have a > null pointer for the filehandle and that fact should be recorded in the > debug log. done. waiting in anticipation for the next hang / crash. Mvh, Frode
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5E1365DC-5717-11D8-B0FA-000A95A9A574>