problems with 2.2.0pre5 and portmap/nfs mount

Achim Kaiser (Achim_Kaiser@t-online.de)
Sat, 09 Jan 1999 14:11:31 +0100


Hi,

I got the following error on booting 2.2.0pre5 while the system trys to
mount the nfs directorys.

Importing Net File System (NFS)portmap: RPC call returned error 111
RPC: task of released request still queued!
RPC: (task is on xprt_pending)
portmap: RPC call returned error 111
RPC: task of released request still queued!
RPC: (task is on xprt_pending)
lockd_up: makesock failed, error=-111
portmap: RPC call returned error 111
RPC: task of released request still queued!
RPC: (task is on xprt_pending)
lockd_up: no pid, 2 users??
[...]

Last 4 lines are repeated several times with increasing users. Then the
bootup sequence halts. No such problems with 2.0.36 .

Achim

CONFIG_M586TSC=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_TSC=y

CONFIG_MODULES=y
CONFIG_KMOD=y

CONFIG_NET=y
CONFIG_PCI_GOANY=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y

CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_IDE=y

CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_PARIDE_PARPORT=y

CONFIG_PACKET=m
CONFIG_UNIX=y
CONFIG_INET=y

CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y

CONFIG_IPX=m

CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_SMC=y
CONFIG_ULTRA=y
CONFIG_PPP=m

CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y

CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=m
CONFIG_PRINTER=y
CONFIG_RTC=y

CONFIG_JOYSTICK=m
CONFIG_JOY_ANALOG=m

CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_MINIX_FS=m
CONFIG_PROC_FS=y
CONFIG_EXT2_FS=y

CONFIG_CODA_FS=m
CONFIG_NFS_FS=m
CONFIG_SUNRPC=m
CONFIG_LOCKD=m
CONFIG_SMB_FS=m

CONFIG_NLS=y

CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_ISO8859_1=m

CONFIG_VGA_CONSOLE=y

CONFIG_SOUND=m
CONFIG_SOUND_OSS=m
CONFIG_SOUND_SB=m

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/