After switching from 2.6.29.2 to 2.6.30-rc5 I get this new message during
boot of my home server:
svc: failed to register lockdv1 RPC service (errno 97).This looks to be the result of the following commit:
commit 363f724cdd3d2ae554e261be995abdeb15f7bdd9
Author: Chuck Lever
SUNRPC: rpcb_register() should handle errors silently
Move error reporting for RPC registration to rpcb_register's caller.Question is: do I really want to know this? I assume the "failure"
happened with previous kernels too, but silently.If I do need to know this, it would be nice if the error was more
informative. I had to grep the kernel source to see that 97 is
-EAFNOSUPPORT and that that means "Address family not supported by
protocol". And even with that I don't know whether it's IPv4 or IPv6
where the failure is.My impression is that this is a bogus message from a user's perspective
and that it should not be displayed.Cheers,
FJP
| Andrew Morton | -mm merge plans for 2.6.23 |
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Mel Gorman | [PATCH 6/8] x86_64 - Specify amount of kernel memory at boot time |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | Re: Soft-Lockup/Race in networking in 2.6.31-rc1+195 ( possibly?caused by netem) |
