Hide Forgot
Description of problem: Just installed kernel-2.6.16-1.2107_FC5 on a x86_64 smp machine. ypbind hangs during boot trying to find a ypserver and rpc.statd was reporting problems too. Rebooting to kernel-2.6.16-1.2096_FC5 works fine. Maybe it's a problem with kernel udp since I grepped these from /var/log/messages: May 3 09:01:40 wintermute rpc.statd[2248]: unable to register (statd, 1, udp). May 3 09:01:40 wintermute ypbind[2383]: Unable to register (YPBINDPROG, YPBINDVERS, udp). May 3 09:19:33 wintermute rpc.statd[2256]: unable to register (statd, 1, udp). May 3 09:19:33 wintermute ypbind[2391]: Unable to register (YPBINDPROG, YPBINDVERS, udp). Version-Release number of selected component (if applicable): kernel-2.6.16-1.2107_FC5 How reproducible: I tried two boots with the same results. Steps to Reproduce: 1. install new kernel 2. reboot 3. Actual results: boot hangs at ypbind and rpc.statd reported some problems that don't seem to be logged completely. Expected results: Additional info:
P.S. selinux is in permissive mode.
Same happen to me, NFS server is RHEL4, /home is mounted. After user login, /home/user works fine, but executing "startx" on client, NFS suddenly dies. ls /home on client hangs.
Similar issue with kernel 2.6.16-1.2107_FC5smp on dual 600MHz Xeon Dell Precision workstation. After boot, accessing a /home directory mounted by NFS from a server results in a hang. Shutdown/reboot hangs when autofs tries to stop. Machine has to be power-cycled to reboot. Also, some files at /home/(user) which are accessed by gnome startup in .gconf or .gconfd get corrupted, and have to be deleted to be able to log back in after successfully booting with the prior kernel. I reproduced this 2 times, and the only change is the kernel version, with 2.6.16-1.2107_FC5smp being the "bad" one.
does booting with pci=nomsi make this go away?
Actually, that option is also broken in this kernel (sigh). 2108, available from http://people.redhat.com/davej/kernels/Fedora/FC5/ has this disabled by default. Give that a try ?
2.6.16-1.2107_FC5smp on Intel(R) Pentium(R) 4 CPU 2.40GHz breaks NFS for me as well. Our diskless LTSP clients failed because they could not mount their root FS. Reverting back to kernel-smp-2.6.16-1.2080_FC5 on the above server solved the problem.
Just tried the 2108 kernel and it does not work for me. Seems to be the same problem.
I have the same problem (x86_64 and i386, with and without SMP), the kernel 2096 work with 2107 ypbind for example fails.
I have problems with NFS, too, both with 2107 and 2108. BUT I'm not running yp, and my problems are on the server side. Should this go in a new bug? FWIW, I have a pcap of the (hung) NFS conversation between the client and the server.
2111 solved my problem