On Sat, Apr 08, 2006 at 09:52:35AM -0400, Rong-En Fan wrote: > On 4/8/06, Kris Kennaway <[EMAIL PROTECTED]> wrote: > > On Sat, Apr 08, 2006 at 01:28:55AM -0400, Rong-En Fan wrote: > > > On 3/6/06, Jun Kuriyama <[EMAIL PROTECTED]> 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=kern/80389 > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/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. > > > > 1.18 was merged 15 months ago, so it cannot be the cause if you > > updated from Feb 2006. > > Yes , I know that. But how to explain that after back-out 1.18 > and restart rpc.lockd, my mutt and irssi will work. And putting > it back, they dont work? I tried backing out and putting back > three times. And, if I simply restart lockd, it does not help.
What doesn't make sense is that it worked on your old system, for which nothing about rpc.lockd was different. Kris
pgp94K4LNQOhK.pgp
Description: PGP signature
