Re: something at init is taking about 31s to finish
Hi.
On Sun, Aug 30, 2015 at 06:58:10AM -0700, briand@aracnet.com wrote:
> On Sun, 30 Aug 2015 13:18:19 +0200
> Sven Hartge <sven@svenhartge.de> wrote:
>
> > briand@aracnet.com wrote:
> > > On Sun, 30 Aug 2015 04:25:36 +0200 Sven Hartge <sven@svenhartge.de> wrote:
> > >> briand@aracnet.com wrote:
> >
> > >>> There's no way anyone can help until i can get a trace of what's
> > >>> going on at boot.
> > >>
> > >> Jessie or newer? With systemd?
> > >>
> > >> systemd-analyze blame
> >
> >
> > > 29.597s networking.service
> > > 3.256s systemd-suspend.service
> >
> > > aha. So I need to dig deeper into networking.service
> >
> > networking.service is /etc/init.d/networking. Somehow the parsing and
> > acting upon /etc/network/interfaces is slow.
> >
> > Please share the contents of /etc/network/interfaces, maybe something
> > odd stands out in there.
> >
>
> cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth0
> iface eth0 inet dhcp
>
> there's this in dmesg:
>
> [ 6.210098] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts:
> (null)
> [ 35.827945] r8169 0000:03:00.0: firmware: failed to load rtl_nic/rtl8168f-1.fw (-2)
> [ 35.827963] r8169 0000:03:00.0: Direct firmware load failed with error -2
> [ 35.827965] r8169 0000:03:00.0: Falling back to user helper
> [ 35.828580] r8169 0000:03:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168f-1.fw (-12)
>
> so it is the dreaded r8169 firmware crappola. the system works fine not loading it.
My-my. Calling perfectly good, working out-of-the box r8169 card like that is way too harsh (and violates this list rules btw).
I happen to have a similar NIC in one of my PCs, and I can confirm that it works flawlessly without any non-free blobs.
I have not tried it with systemd, though.
> is there any way to tell the module to not even try and load it ?
Why are you so sure that it's the failing firmware loading that adds 30 seconds to your boot sequence? According to the dmesg, the whole ("I need firmware - oh well, I'll try without it") takes whooping 600us.
Start with something simple. Like replacing dhcp configuration with static IP assignment.
Continue with obligatory "in the case of the doubt fallback to sysvinit".
Finally, dump the network traffic during the boot of the offending host (requires and extra host or some trickery, though).
Reco
Reply to: