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 <chuck.lever@oracle.com>
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| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Rafael J. Wysocki | Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4d... |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
