From owner-freebsd-current@FreeBSD.ORG Fri Feb 13 01:22:18 2004 Return-Path: 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 9BA5216A4CE for ; Fri, 13 Feb 2004 01:22:18 -0800 (PST) Received: from emmi.physik.TU-Berlin.DE (emmi.physik.TU-Berlin.DE [130.149.160.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE99D43D1F for ; Fri, 13 Feb 2004 01:22:17 -0800 (PST) (envelope-from jschlesn@emmi.physik.TU-Berlin.DE) Received: from emmi.physik.TU-Berlin.DE (localhost.physik.TU-Berlin.DE [127.0.0.1])i1D9M6F6010489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Feb 2004 10:22:06 +0100 (CET) (envelope-from jschlesn@emmi.physik.TU-Berlin.DE) Received: (from jschlesn@localhost)i1D9LuBO010472; Fri, 13 Feb 2004 10:21:56 +0100 (CET) (envelope-from jschlesn) Date: Fri, 13 Feb 2004 10:21:56 +0100 From: Jan Schlesner To: Frode Nordahl Message-ID: <20040213092156.GA7928@physik.TU-Berlin.DE> References: <0703C4CC-5805-11D8-951F-000A95A9A574@nordahl.net> <20040205231849.D41237@mail.allcaps.org> <56C69560-5BAF-11D8-A6E1-000A95A9A574@nordahl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56C69560-5BAF-11D8-A6E1-000A95A9A574@nordahl.net> User-Agent: Mutt/1.4.1i X-Url: X-PGP-Key: X-Operating-System: FreeBSD 4.9-RELEASE-p2, i386 X-Mailer: Mutt 1.4.1i ( i386 FreeBSD 4.9-RELEASE-p2 ) X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Fri, 13 Feb 2004 05:23:30 -0800 cc: "Andrew P. Lentvorski, Jr." cc: current@freebsd.org Subject: Re: rpc.lockd(8) seg faults on 5.2-RELEASE (patch, workaround) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 13 Feb 2004 09:22:19 -0000 Hi, the workaround doesn't work on my computer. With this patch I don't see any change in the behaviour of the rpc.lockd. After a few hours the rpc.lockd stops with the signal 11 (only the process with the uid 0). Is there someone working on the PR kern/61122 or PR bin/61718? Jan On Tue, Feb 10, 2004 at 10:56:04AM +0100, Frode Nordahl wrote: > This is not a sollution, but I have run with this workaround since > friday without incident. > > I think there are two problems: > - freed items are sometimes not removed from the nfslocklist > - first element in blockedlocklist sometimes get wrong, causing a > infinite loop in retry_blockingfilelocklist() > On Feb 6, 2004, at 08:21, Andrew P. Lentvorski, Jr. wrote: > > >On Thu, 5 Feb 2004, Frode Nordahl wrote: > > > >>I also found this in send_granted(): lockd_lock.c:2161 > >> > >> debuglog("About to send granted on blocked lock\n"); > >> sleep(1); > >> debuglog("Blowing off return send\n"); > >> > >>Anyone know what sleep(1) is good for here? > > > >The sleep() statements near debuglog() stuff are to work around the > >fact > >that syslog has bugs where it arbitrarily and randomly eats messages > >when > >you start sending too much data at it too quickly. > > > >By slowing down the logging, all of the messages get recorded. -- [ gpg key: http://wwwds.physik.tu-berlin.de/~jan/jschlesn.gpg ] [ key fingerprint: 4236 3497 C4CF 4F3A 274F B6E2 C4F6 B639 1DF4 CF0A ] -- It's better to reign in hell, than to serve in heaven...