Hi gustavo, thanks for taking the time to file this bug report.
Network interfaces have two modes. One is /etc/network/interfaces, and the other is NetworkManager. Which are you using? The former will bring up any interfaces as soon as udev detects them. It will also do a blanket bring up of any interfaces that aren't udev detected (like bridges and bonded interfaces) after udevtrigger finishes.
The latter starts later, and is my dynamic about interfaces.
Anyway, can you try booting with '--verbose noquiet' added to the kernel command line so we can see the messages being printed out. This should give an idea of what upstart jobs and services are being started that might be blocking the rest of the boot.
Hi gustavo, thanks for taking the time to file this bug report.
Network interfaces have two modes. One is /etc/network/ interfaces, and the other is NetworkManager. Which are you using? The former will bring up any interfaces as soon as udev detects them. It will also do a blanket bring up of any interfaces that aren't udev detected (like bridges and bonded interfaces) after udevtrigger finishes.
The latter starts later, and is my dynamic about interfaces.
Anyway, can you try booting with '--verbose noquiet' added to the kernel command line so we can see the messages being printed out. This should give an idea of what upstart jobs and services are being started that might be blocking the rest of the boot.