Bug#783779: systemd: system-ifup.slice start completes before interface is up

[Michael Biebl]

Am 30.04.2015 um 01:47 schrieb Karl Kornel:
> Package: systemd
> Version: 215-17
> Severity: normal
> 
> Hello!
> 
> I have a system, with a third-party network card using non-free firmware, where 
> systemd does not wait for the interface to come up before continuing boot.
> 
> The card uses the rtl_nic/rtl8168e-2.fw firmware file from the firmware-realtek 
> package.  When systemd wants to start the network, this firmware file is 
> direct-loaded, causing the link to go down for a couple of seconds.  However, 
> the rest of the boot process (including DHCP, NTP, OpenAFS, etc.) is already 
> continuing, while the interface is still down.

Once /etc/init.d/networking has completed, the network is considered up.

> I am attaching the systemd journal, from boot up to the point where all of the 
> network-using services are normal.  The firmware load (and issues) start around 
> line 1034.


Can you attach the output of
systemctl status networking.service
systemctl status ifup at eth0.service

(you need to run that as root).
Does it help, if you switch "allow-hotplug eth0" to "auto eth0" in
/etc/network/interfaces?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150430/931c89f3/attachment-0002.sig>