RPC errors.. in 2.1.119

Charlie Ross (rossc@cs.colostate.edu)
Sat, 5 Sep 1998 03:21:04 -0600 (MDT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Harald Koenig: "Re: 2.1.119 FourPort serial interrupt probing broken"
Previous message: Hans Reiser: "Re: (reiserfs) Re: Implementing Meta File information in Linux (and why not just use gdbm, or MIME,"

I just upgraded from 2.0.34 to 2.1.199, and now I am getting messages about
RPC errors. Nothing has changed except the kernel, they happen just after
it begins mounting remote filesystems upon boot..

kernel: portmap: RPC call returned error 111
kernel: RPC: task of released request still queued!
kernel: RPC: (task is on xprt_pending)
kernel: portmap: RPC call returned error 111
kernel: RPC: task of released request still queued!
kernel: RPC: (task is on xprt_pending)
kernel: lockd_up: makesock failed, error=-111
kernel: portmap: RPC call returned error 111
kernel: RPC: task of released request still queued!
kernel: RPC: (task is on xprt_pending)

-
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/faq.html

Next message: Harald Koenig: "Re: 2.1.119 FourPort serial interrupt probing broken"
Previous message: Hans Reiser: "Re: (reiserfs) Re: Implementing Meta File information in Linux (and why not just use gdbm, or MIME,"