From owner-freebsd-stable@FreeBSD.ORG  Sat Apr  8 05:28:56 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: stable@freebsd.org
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E6E2416A423
	for <stable@freebsd.org>; Sat,  8 Apr 2006 05:28:56 +0000 (UTC)
	(envelope-from grafan@gmail.com)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 78D0043D45
	for <stable@freebsd.org>; Sat,  8 Apr 2006 05:28:56 +0000 (GMT)
	(envelope-from grafan@gmail.com)
Received: by zproxy.gmail.com with SMTP id l8so527261nzf
	for <stable@freebsd.org>; Fri, 07 Apr 2006 22:28:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=scdRxzwUxBL2VEPiCHiJ1AJLR2fFwmQOD2Y4dz0NfhhJsr2nNmVMHqWLUA+pHWVM5mSavo6Ke53GTN2/1hQM0vu16DAQPS0mvq/Oy0iifpYro4P51AHtsYLWbQOablF3ZRWkQ8U5s1YAf1BP49VlhgoWkhkLJqwZ38Ijwevysp8=
Received: by 10.37.15.33 with SMTP id s33mr1723631nzi;
	Fri, 07 Apr 2006 22:28:55 -0700 (PDT)
Received: by 10.36.57.15 with HTTP; Fri, 7 Apr 2006 22:28:55 -0700 (PDT)
Message-ID: <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com>
Date: Sat, 8 Apr 2006 01:28:55 -0400
From: "Rong-En Fan" <grafan@gmail.com>
To: "Jun Kuriyama" <kuriyama@imgsrc.co.jp>
In-Reply-To: <7mveururc6.wl%kuriyama@imgsrc.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <7mveururc6.wl%kuriyama@imgsrc.co.jp>
Cc: stable@freebsd.org
Subject: Re: rpc.lockd brokenness (2)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Apr 2006 05:28:57 -0000

On 3/6/06, Jun Kuriyama <kuriyama@imgsrc.co.jp> wrote:
>
> I'm not yet received enough information to track rpc.lockd problem.
>
> As Kris posted before, here is a patch to backout my suspected
> commit.  If someone can easily reproduce this problem, please try with
> this patch on both of server/client side of rpc.lockd (I'm not sure
> which of server/client side this affects).
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/80389
> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84953
>
> Any reports about this patch (OK or still problem) are welcome!

Hi,

Somehow I have problems with lockd after 3 boxes upgraded from
Feb's RELENG_6 to Apr 6's. One of them has problems with lockd.
For example, mutt and irssi will stuck in lockd (shown by
top). I tried to back out changes in revision 1.18 for lock_proc.c,
and do /etc/rc.d/nfslocking stop then a start. After backout it,
mutt and irssi work well. If I put 1.18 back, mutt and irssi will stuck
in lockd again.

Last month, I played with the test program/script in those two PRs,
found that revision 1.18 does not make any difference. I'm not 100%
sure the problem I encountered now is related to rev 1.18. But
it is a report that  backout 1.18 really helps.

For record, all my clients involved in this mail are running RELENG_6.
Server is RELENG_5 as of March 9. Only IPv4 here, no IPv6.

Regards,
Rong-En Fan