* Karl Sinn [02-13-14 03:33]:

Am 13.02.2014 07:49, schrieb Wolfgang Rosenauer:

...

blame" and "systemd-analyze plot > output.svg" to get a picture of what is taking so long on your boot? So now I completely replaced my hardware with a very powerful completely new one. Latest Intel core i5 Haswell + SSD. No software raid anymore. Just a very simple setup with one disk. And I'm still really wondering how you can boot that fast. My boot time is regularly still 45 seconds (almost exactly the same as with my old hardware).

Hygiea:~ # systemd-analyze blame 30.883s systemd-udev-settle.service 5.825s network.service 5.427s network@enp0s25.service 3.034s cifs.service 1.000s systemd-vconsole-setup.service ...

What is this systemd-udev-settle.service doing? Nobody could tell me so far. Could it be related to USB devices? I have some of them connected which have card readers attached. The network service also is a bit strange given that it is a static configuration.

[...]

I wonder since I installed 13.1 why the boot process takes so long. Thanks to your message I learned about "systemd-analyze blame". In my situation also network and systemd-udev-settle.service take long to do their jobs, but the other way round:

systemd-analyze blame 26.459s network.service 24.541s network@enp2s5.service 5.947s systemd-udev-settle.service 2.903s plymouth-start.service

How I can I figure out in detail why it hangs? And how do I change this?

I am in the same: My older server box w/no ssd: 15.737s mysql.service 15.254s apache2.service 8.421s smb.service 7.694s SuSEfirewall2.service 6.419s plymouth-start.service 6.271s systemd-udev-settle.service 6.259s network.service 5.240s network@eth0.service My desktop work station w/ssd for system: 21.945s network.service 20.906s network@eth0.service 3.126s ntp.service 2.047s systemd-udev-settle.service 1.338s spamd.service 1.181s SuSEfirewall2.service 1.020s privoxy.service -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Feb 13, 2014 at 5:04 PM, Carlos E. R. wrote:

Funny about the lvm, as I have no lvm here.

It cannot know whether you have volume groups or not. Hopefully second attempt to switch to event-based activation will be more successful. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 13/02/2014 14:28, Carlos E. R. a écrit :

I know that, but it takes 4 seconds to find out.

most of the tasks are in //, obviously jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-13 14:55, Malcolm wrote:

On Thu 13 Feb 2014 02:28:08 PM CST, Carlos E. R. wrote:

...

...

It cannot know whether you have volume groups or not.

I know that, but it takes 4 seconds to find out.

Hi But is it in the critical chain?

Hum. You got a point there. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL84KQACgkQja8UbcUWM1wCFgD/TPTMvLkfqni52b89P99ptLPS XtGS54m/JZcrXnSpcKMA/2AlvKwqs9XXqbCMH1i3aUPrfBKDut784/LwiX/7MaJl =TXai -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Feb 13, 2014 at 2:29 PM, jdd wrote:

mine, with ssd:

# systemd-analyze Startup finished in 5.041s (kernel) + 22.884s (userspace) = 27.925s

on this old (3 year) computer, the (new) ssd did really makes things faster

I don't know if this helps the discussion much.. Here's mine from an updated 13.1 (install is about 2 weeks old). # systemd-analyze Startup finished in 2.421s (kernel) + 1.955s (userspace) = 4.376s # systemd-analyze blame 785ms vmware.service 716ms systemd-udev-settle.service 532ms plymouth-start.service 186ms nfs.service 179ms dkms_autoinstaller.service 172ms apparmor.service 134ms mnt-windows.mount 98ms plymouth-read-write.service .... (truncated)

From Grub to desktop is barely measurable/noticeable... as in it's stinking fast. That's with VMWare, NFS mounts etc. in there.

C. -- openSUSE 13.1 x86_64, KDE 4.12 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am 13.02.2014 14:04, schrieb Carlos E. R.:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2014-02-13 13:55, Patrick Shanahan wrote:

...

My desktop work station w/ssd for system:

21.945s network.service 20.906s network@eth0.service 3.126s ntp.service 2.047s systemd-udev-settle.service 1.338s spamd.service 1.181s SuSEfirewall2.se This laptop, no ssd:

7.082s spamd.service 5.671s systemd-fsck@dev-disk-by\x2dlabel-Boot.service 5.613s systemd-fsck@dev-disk-by\x2dlabel-Other.service 4.970s systemd-fsck@dev-disk-by\x2dlabel-Home.service 4.159s lvm2-activation.service 3.412s windows-C.mount 3.315s xdm.service 2.503s lvm2-activation-early.service 2.185s NetworkManager.service

Funny about the lvm, as I have no lvm here.

You can try instead "systemd-analyze critical-chain". Mine:

The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character.

graphical.target @26.468s └─helloworld.service @26.073s +394ms └─multi-user.target @26.071s └─spamd.service @18.988s +7.082s └─basic.target @18.929s └─timers.target @18.922s └─systemd-tmpfiles-clean.timer @18.922s └─sysinit.target @18.913s └─apparmor.service @18.535s +377ms └─systemd-tmpfiles-setup.service @18.027s +503ms └─local-fs.target @17.629s └─other.mount @16.395s +1.232s

└─systemd-fsck@dev-disk-by\x2dlabel-Other.service @10.730s +5.613s └─dev-disk-by\x2dlabel-Other.device @10.726s minas-tirith:~ #

here it looks like this: graphical.target @3w 6d 2h 26min 52.163s └─multi-user.target @41.153s └─cron.service @41.147s └─postfix.service @39.919s +1.225s └─time-sync.target @39.912s └─ntp.service @39.638s +248ms └─nss-lookup.target @39.610s └─network.target @39.601s └─network.service @13.141s +26.459s └─SuSEfirewall2_init.service @11.144s +1.995s └─basic.target @11.116s It's hanging at network.service. How can I find out what's the problem, and how to fix it? thanks Karl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am 13.02.2014 15:10, schrieb Dylan:

On 13/02/14 13:55, Karl Sinn wrote:

...

It's hanging at network.service.

How can I find out what's the problem, and how to fix it?

How long does it take for the DHCP server to respond?

it's my local router: ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.459 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.417 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.469 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.482 ms Karl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

No, that's not it. DHCP, for reasons I don't clearly know, is often very slow to respond. I guess the method tries something which fails, but has to wait for the timeouts before trying another way.

How do I check that? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org