Comment 9 for bug 1167337

On Tuesday 23 April 2013, Steve Langasek wrote:
> > So an other possibility is, that longer delay of dhcpclient cause the
> > problem for mounting the nfs-fs.
>
> The handling of both ifupdown and network-manager is designed such that
> the interface should not be considered 'up' until dhclient succeeds. If
> 'sudo initctl list' is showing the interface as up in this case, then
> that's a bug; more likely, however, the interface is either still
> waiting for a dhcp answer or is considered failed, and bringing up the
> interface will bring up the NFS mounts as well. Either way, that's
> obviously not a bug in the NFS packages, since if the network has no
> address NFS can't work.
This problem is not on a nfs machine. At the moment I have solved this problem
with a broadcom addon card, which works more reliable than the built in Intel
card. Maybe this is a e1000 driver issue.
>
> > Is there a possibility to restart dhcpclient in case of a unsuccessful
> > inquiry.
>
> "ifdown eth0; ifup eth0"
>
> Please let us know if you find that the new version of the upstart jobs
> solves the nfs problem (but not the network problem, obviously). If it
> does, that strengthens the argument for pushing this fix as a stable
> release update to 12.04.

Until now your new upstart scripts seams to work ok.
I have not been able to reproduce the boot hang in about 10 starts, but a
hot-boot was already successful most times.
But my 2 test users have not reported any problems this week (2 coldboots
until now). I will report you the "long term" results end of the week.