freebsd stable - Jun 2005 - RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive

Hi,

I have upgraded fresh installed 5.4-RELEASE to 5.4-STABLE today. With 5.4R 
I was able to mount nfs from another 5.4R box. But after I did cvsup and 
buildworld and buildkernel today, I'm no longer able to use nfs. This is 
what I get when I try mount:

RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive

This message is what I get whenever I try mounting anything with nfs no 
matter is it exported or not or no matter does host exists or not like 
this:

hosting# mount 10.10.10.10:/backup /mnt
[udp] 10.10.10.10:/backup: RPCPROG_NFS: RPC: Port mapper failure - RPC: 
Unable to receive
^C
hosting# mount 1.1.1.1:/blabla /mnt
[udp] 1.1.1.1:/blabla: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable 
to receive
^C
hosting# mount 255.255.255.255:/blabla /mnt
[udp] 255.255.255.255:/blabla: RPCPROG_NFS: RPC: Port mapper failure - 
RPC: Unable to receive
^C
hosting#



Regards,
gg.

On Thursday 09 June 2005 12:42, Goran Gajic wrote:
> Hi,
>
> RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
>
(jmg: I cc'd you on the off chance you have not seen this already, another 
user identified your changes as related, but I have not tested this myself.)

Yes, it seems that changes to the kernel (specifically kqueue?) broke NFS (and 
other things) in -STABLE. See these messages for related reports.

1 <20050608002333.73758.qmail@web26206.mail.ukl.yahoo.com>
2 <20050609013258.GB85828@blazingdot.com>

HTH,
-- 
Dominic
GoodforBusiness.co.uk
I.T. Services for SMEs in the UK.

Dominic Marks wrote this message on Thu, Jun 09, 2005 at 12:56
+0100:
> On Thursday 09 June 2005 12:42, Goran Gajic wrote:
> > Hi,
> >
> > RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
> >
> 
> (jmg: I cc'd you on the off chance you have not seen this already,
another
> user identified your changes as related, but I have not tested this
myself.)
> 
> Yes, it seems that changes to the kernel (specifically kqueue?) broke NFS
(and
> other things) in -STABLE. See these messages for related reports.
could you try backing out uipc_socket.c v1.208.2.19?  If it broke because
of my commits, it would of been this one, though I'm puzzeled as to why
it didn't break in -current...

P.S. Could you teach your mailer not to cc -stable twice?  (once as
freebsd.org and again as www.freebsd.org)

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."

> -----Original Message-----
> From: owner-freebsd-stable@freebsd.org 
> [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of 
> John-Mark Gurney
> Sent: Thursday, June 09, 2005 11:45 AM
> To: Dominic Marks
> Cc: Goran Gajic; freebsd-stable@freebsd.org
> Subject: Re: RPCPROG_NFS: RPC: Port mapper failure - RPC: 
> Unable to receive
> 
> Dominic Marks wrote this message on Thu, Jun 09, 2005 at 12:56 +0100:
> > On Thursday 09 June 2005 12:42, Goran Gajic wrote:
> > > Hi,
> > >
> > > RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
> > >
> > 
> > (jmg: I cc'd you on the off chance you have not seen this already,
> > another user identified your changes as related, but I have 
> not tested 
> > this myself.)
> > 
> > Yes, it seems that changes to the kernel (specifically 
> kqueue?) broke 
> > NFS (and other things) in -STABLE. See these messages for 
> related reports.
> 
> could you try backing out uipc_socket.c v1.208.2.19?  If it 
> broke because of my commits, it would of been this one, 
> though I'm puzzeled as to why it didn't break in -current...
I can vouch for that:

# diff -u yp.kernel.good yp.kernel.bad 
--- yp.kernel.good      Tue Jun  7 14:24:43 2005
+++ yp.kernel.bad       Tue Jun  7 14:24:54 2005
@@ -82,7 +82,7 @@
      $FreeBSD: src/sys/kern/kern_descrip.c,v 1.243.2.7 2005/04/23 21:53:04
ps Exp $
      $FreeBSD: /repoman/r/ncvs/src/sys/kern/kern_poll.c,v 1.19 2005/02/25
22:07:50 trhodes Exp $
      $FreeBSD: src/sys/kern/kern_environment.c,v 1.34.2.2 2005/03/10
17:09:16 des Exp $
-     $FreeBSD: src/sys/kern/kern_event.c,v 1.79.2.7 2005/04/21 21:11:24 ps
Exp $
+     $FreeBSD: src/sys/kern/kern_event.c,v 1.79.2.8 2005/06/07 06:35:10 jmg
Exp $
      $FreeBSD: src/sys/kern/kern_exec.c,v 1.249.2.5 2005/02/27 02:40:09 jeff
Exp $
      $FreeBSD: src/sys/kern/kern_exit.c,v 1.245.2.11 2005/04/27 13:00:29
davidxu Exp $
      $FreeBSD: src/sys/kern/kern_fork.c,v 1.234.2.9 2005/04/27 11:32:23
davidxu Exp $
@@ -173,7 +173,7 @@
      $FreeBSD: src/sys/kern/uipc_mbuf.c,v 1.135.2.5 2005/05/11 21:54:43 emax
Exp $
      $FreeBSD: src/sys/kern/uipc_mbuf2.c,v 1.26.2.1 2005/01/31 23:26:17 imp
Exp $
      $FreeBSD: src/sys/kern/uipc_proto.c,v 1.24 2004/04/05 21:03:36 imp Exp
$
-     $FreeBSD: src/sys/kern/uipc_socket.c,v 1.208.2.18 2005/03/31 22:35:23
sobomax Exp $
+     $FreeBSD: src/sys/kern/uipc_socket.c,v 1.208.2.19 2005/06/07 07:11:03
jmg Exp $
      $FreeBSD: src/sys/kern/uipc_socket2.c,v 1.137.2.6 2005/04/01 05:34:18
rwatson Exp $
      $FreeBSD: src/sys/kern/uipc_syscalls.c,v 1.200.2.8 2005/05/11 21:54:43
emax Exp $
      $FreeBSD: src/sys/kern/uipc_usrreq.c,v 1.138.2.14 2005/05/08 10:19:37
cperciva Exp $

I can also confirm that mount of NFS exports works ok with uipc_socket.c 
v1.208.2.18 - so there are some problems with v1.208.2.19

Regards,
gg.