Re: something at init is taking about 31s to finish
On 2015-08-31, wrote: > >> I understand the whole "oh noes, firmware is a binary blob with unknown >> contents [...] > > It seems you don't :-) > >> By not installing the firmware package, you are just making your life >> harder without gaining anything but a delayed boot. > > There sure should be anoher way? > You could always use that thirty seconds to read, for example: Buffalo Bill's defunct who used to ride a watersmooth-silver stallion and break onetwothreefourfive pigeonsjustlikethat Jesus he was a handsome man and what i want to know is how do you like your blueeyed boy Mister Death Among so many others. Just a thought. Curt
Re: something at init is taking about 31s to finish
On Mon, 31 Aug 2015 11:56:09 +0300
Reco wrote:
> > there's this in dmesg:
> >
> > [6.210098] EXT4-fs (sda7): mounted filesystem with ordered data mode.
> > Opts:
> > (null)
> > [ 35.827945] r8169 :03:00.0: firmware: failed to load
> > rtl_nic/rtl8168f-1.fw (-2)
> > [ 35.827963] r8169 :03:00.0: Direct firmware load failed with error -2
> > [ 35.827965] r8169 :03:00.0: Falling back to user helper
> > [ 35.828580] r8169 :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.
>
> 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.
That's true, the messages are somewhat ambiguous.
ah well. guess i'll try loading the firmware and see if that's the problem as
Brian suggested.
Brian
Re: something at init is taking about 31s to finish
On Mon 31 Aug 2015 at 11:56:09 +0300, Reco wrote:
> On Sun, Aug 30, 2015 at 06:58:10AM -0700, bri...@aracnet.com wrote:
> >
> > there's this in dmesg:
> >
> > [6.210098] EXT4-fs (sda7): mounted filesystem with ordered data mode.
> > Opts:
> > (null)
> > [ 35.827945] r8169 :03:00.0: firmware: failed to load
> > rtl_nic/rtl8168f-1.fw (-2)
> > [ 35.827963] r8169 :03:00.0: Direct firmware load failed with error -2
> > [ 35.827965] r8169 :03:00.0: Falling back to user helper
> > [ 35.828580] r8169 :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.
The Installation Guide mentions that some hardware works well without
firmware. It's a matter of trying it and seeing how you go on.
> > 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).
Booting with the firmware loaded should settle the question about the
30 second delay being a caused by its lack.
Re: something at init is taking about 31s to finish
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Aug 31, 2015 at 11:56:09AM +0300, Reco wrote: > Hi. > > On Sun, Aug 30, 2015 at 06:58:10AM -0700, bri...@aracnet.com wrote: [...] > > 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). My feeling would be that calling network cards (and firmwares) names would be OK. Unless those are people, that is :-) - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlXkJPAACgkQBcgs9XrR2kZdyACeLKnqX0lloOj6cHcETbJrums9 rFQAn09hKPIaQwu6dzRe9HRjcJ11CTis =CfF5 -END PGP SIGNATURE-
Re: something at init is taking about 31s to finish
Hi.
On Sun, Aug 30, 2015 at 06:58:10AM -0700, bri...@aracnet.com wrote:
> On Sun, 30 Aug 2015 13:18:19 +0200
> Sven Hartge wrote:
>
> > bri...@aracnet.com wrote:
> > > On Sun, 30 Aug 2015 04:25:36 +0200 Sven Hartge wrote:
> > >> bri...@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 :03:00.0: firmware: failed to load
> rtl_nic/rtl8168f-1.fw (-2)
> [ 35.827963] r8169 :03:00.0: Direct firmware load failed with error -2
> [ 35.827965] r8169 :03:00.0: Falling back to user helper
> [ 35.828580] r8169 :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
Re: something at init is taking about 31s to finish
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Aug 31, 2015 at 12:39:14AM +0200, Sven Hartge wrote: > bri...@aracnet.com wrote: > > > [6.210098] EXT4-fs (sda7): mounted filesystem with ordered data mode. > > Opts: > > (null) > > [ 35.827945] r8169 :03:00.0: firmware: failed to load > > rtl_nic/rtl8168f-1.fw (-2) > > [ 35.827963] r8169 :03:00.0: Direct firmware load failed with error -2 > > [ 35.827965] r8169 :03:00.0: Falling back to user helper > > [ 35.828580] r8169 :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. is there any way to tell the module to not even try > > and load it ? > > "modinfo r8169" tells me: no, there is not. > > Why not just install the package "firmware-realtek" and be done with it? There might be opinions on that that (GASP!) differ from yours. > I understand the whole "oh noes, firmware is a binary blob with unknown > contents [...] It seems you don't :-) > By not installing the firmware package, you are just making your life > harder without gaining anything but a delayed boot. There sure should be anoher way? - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlXkCysACgkQBcgs9XrR2kZrEQCbBuMiCbKrTj3Dp2LSqrrEDyz1 wcQAn2PMMGl94eCBlSCAFDZ3glkKcjeX =NJwM -END PGP SIGNATURE-
Re: something at init is taking about 31s to finish
bri...@aracnet.com wrote: > [6.210098] EXT4-fs (sda7): mounted filesystem with ordered data mode. > Opts: > (null) > [ 35.827945] r8169 :03:00.0: firmware: failed to load > rtl_nic/rtl8168f-1.fw (-2) > [ 35.827963] r8169 :03:00.0: Direct firmware load failed with error -2 > [ 35.827965] r8169 :03:00.0: Falling back to user helper > [ 35.828580] r8169 :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. is there any way to tell the module to not even try > and load it ? "modinfo r8169" tells me: no, there is not. Why not just install the package "firmware-realtek" and be done with it? I understand the whole "oh noes, firmware is a binary blob with unknown contents, woe me, woe me, the NSA is gonna hack me" stance, but in this case, the unknown binary blob is already active in the NIC, the firmware file merely provides an update. By not installing the firmware package, you are just making your life harder without gaining anything but a delayed boot. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: something at init is taking about 31s to finish
On Sun, 30 Aug 2015 13:18:19 +0200 Sven Hartge wrote: > bri...@aracnet.com wrote: > > On Sun, 30 Aug 2015 04:25:36 +0200 Sven Hartge wrote: > >> bri...@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 :03:00.0: firmware: failed to load rtl_nic/rtl8168f-1.fw (-2) [ 35.827963] r8169 :03:00.0: Direct firmware load failed with error -2 [ 35.827965] r8169 :03:00.0: Falling back to user helper [ 35.828580] r8169 :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. is there any way to tell the module to not even try and load it ? Brian
Re: something at init is taking about 31s to finish
bri...@aracnet.com wrote: > On Sun, 30 Aug 2015 04:25:36 +0200 Sven Hartge wrote: >> bri...@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. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: something at init is taking about 31s to finish
On Sun, 30 Aug 2015 04:25:36 +0200 Sven Hartge wrote: > bri...@aracnet.com wrote: > > > it almost looks like something is timing out, and yet the system works > > fine, so whatever it is that the process is waiting on it doesn't seem > > to matter. > > > i have a bad feeling it's the dreade ethernet firmware loading thing > > (just a guess) since that's the message that comes up immediately > > after the wait finishes. > > > 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 i've been playing around with systemd-analyze but i can't seem to figure out how to resolve what i'm sure must be the pieces living inside networking.service. Brian
Re: something at init is taking about 31s to finish
bri...@aracnet.com wrote: > it almost looks like something is timing out, and yet the system works > fine, so whatever it is that the process is waiting on it doesn't seem > to matter. > i have a bad feeling it's the dreade ethernet firmware loading thing > (just a guess) since that's the message that comes up immediately > after the wait finishes. > 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 Grüße, Sven. -- Sigmentation fault. Core dumped.
