Comment 6 for bug 19196

(In reply to comment #5)
> The kernel has nothing to do with it. My hack solution to make this always working
> was to run a tcpdump session on the server and see that the client was connecting
> and while the server was answering, the client did timeout.

What did you see in the tcpdump session which showed that it was nfsmount and
not the kernel which was responsible for the traffic?

> If this is a race condition, than it's due to something not loading the driver
> in time or not waiting for the stuff to be configured properly before using them.

The driver is obviously loaded and working, because the interface exists and
DHCP worked. ipconfig does DHCP and configures the interface before exiting.
Where is it that you feel it should wait?

Adding a sleep before attempting the NFS mount, as I have done to work around
this problem, is not the correct solution.