Booting openSUSE Leap 42.1 extremely slow

JZL240I-U · 03-24-2016, 12:26 PM

Hardware is the PC in my signature.

This is what I tried:

Code:

me@PC:~> systemd-analyze critical-chain
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 @21.572s
└─display-manager.service @19.179s +2.393s
  └─time-sync.target @19.176s
    └─ntpd.service @18.286s +888ms
      └─network.target @18.201s
        └─NetworkManager.service @17.958s +242ms
          └─SuSEfirewall2_init.service @9.530s +8.425s
            └─basic.target @8.824s
              └─timers.target @8.824s
                └─systemd-tmpfiles-clean.timer @8.824s
                  └─sysinit.target @8.823s
                    └─apparmor.service @8.274s +548ms
                      └─systemd-tmpfiles-setup.service @5.657s +2.615s
                        └─local-fs.target @5.648s
                          └─home.mount @5.405s +240ms
                            └─systemd-fsck@dev-disk-by\x2duuid-72719c81\x2d1f89\x2d4d11\x2da669\x2dcf6305c9a1ed.service @4.371s +1.033s
                              └─dev-disk-by\x2duuid-72719c81\x2d1f89\x2d4d11\x2da669\x2dcf6305c9a1ed.device @4.369s

me@PC:~> systemd-analyze blame
          8.895s avahi-daemon.service
          8.425s SuSEfirewall2_init.service
          2.615s systemd-tmpfiles-setup.service
          2.393s display-manager.service
          2.183s vboxdrv.service
          2.028s dev-sda8.device                                                                                                                      
          1.706s wpa_supplicant.service                                                                                                               
          1.550s systemd-fsck@dev-disk-by\x2duuid-2618c23e\x2ddba9\x2d4e58\x2da69f\x2d75e2fee34286.service                                            
          1.417s postfix.service                                                                                                                      
          1.387s nscd.service                                                                                                                         
          1.372s var-lib-mailman.mount                                                                                                                
          1.365s var-lib-mariadb.mount                                                                                                                
          1.362s var-lib-libvirt-images.mount                                                                                                         
          1.319s var-log.mount                                                                                                                        
          1.074s boot-grub2-i386\x2dpc.mount                                                                                                          
          1.064s var-lib-mysql.mount                                                                                                                  
          1.051s var-lib-pgsql.mount                                                                                                                  
          1.050s var-lib-named.mount                                                                                                                  
          1.045s var-crash.mount                                                                                                                      
          1.044s var-opt.mount                                                                                                                        
          1.043s boot-grub2-x86_64\x2defi.mount                                                                                                       
          1.035s opt.mount
          1.033s systemd-fsck@dev-disk-by\x2duuid-72719c81\x2d1f89\x2d4d11\x2da669\x2dcf6305c9a1ed.service
           988ms var-tmp.mount
           954ms srv.mount
           932ms usr-local.mount
           888ms ntpd.service
           837ms SuSEfirewall2.service
           816ms dev-disk-by\x2duuid-b7f0fdef\x2de97f\x2d48fa\x2d9a73\x2d3e74373df4c5.swap
           708ms sys-kernel-debug.mount
           670ms tmp.mount
           647ms var-spool.mount
           548ms apparmor.service
           527ms systemd-journald.service
           511ms upower.service
           465ms systemd-user-sessions.service
           448ms systemd-udev-trigger.service
           405ms systemd-remount-fs.service
           404ms udisks2.service
           400ms dev-mqueue.mount
           400ms dev-hugepages.mount
           330ms systemd-modules-load.service

Then:

Code:

me@PC:~> systemd-analyze
Startup finished in 2.017s (kernel) + 2.296s (initrd) + 21.582s (userspace) = 25.896s

me@PC:~> systemd-analyze plot > boot4.svg

In stark reality it is even slower, about one minute to graphical login and another 30 seconds to the GUI. Lots of disk activity. When I had Mint running prior to booting SUSE time may go up to two and a half minutes.

Darn. How do I attach a file here? I wanted to post the plot but I don't find how to do that...

John VV · 03-24-2016, 12:53 PM

i find it easier to have "systemd-analyze" output a svg image and SEE what is causing the roadblock

the svg is set up to show the time and sequence of booting

most of the time the network connection is a roadblock
or the ati/nvidia driver

as to the plot
convert the svg to a png ( using Gimp) and use imgur or imgbox
-- the image is BIG, imgbox has a 10 meg file size max

this is a few years old
https://lizards.opensuse.org/2012/07...2-second-boot/

or a post on the suse forum
https://forums.opensuse.org/showthre...-time-openSUSE

i am booting 13.2 at 45 sec. on a 5 year old computer
http://imgbox.com/njo6GCdt

JZL240I-U · 03-24-2016, 01:15 PM

Quote:

Originally Posted by John VV

i find it easier to have "systemd-analyze" output a svg image and SEE what is causing the roadblock

That's what I did. I wanted to show the plot here, but somehow the "attach file" box doesn't work on LQ?!?

Quote:

Originally Posted by John VV

most of the time the network connection is a roadblock
or the ati/nvidia driver

It seems to be the firewall.

Quote:

Originally Posted by John VV

convert the svg to a png ( using Gimp)

Already done (created a .jpg)

Quote:

Originally Posted by John VV

and use imgur or imgbox
-- the image is BIG, imgbox has a 10 meg file size max

Why not post the svg then? <edit> Ah, they're not accepted. Neither imgur nor imgbox work for me (image too large or no reaction on clicking upload

). But why doesn't it work on LQ? </edit>

<edit2> Also I don't really know how to interpret the systemd blame plots </edit2>

Will read the links now, thanks.