Arch Linux

rabipoudel

Member

Registered: 2020-05-13

Posts: 2

Slow boot time into graphical.target?

My system is booting too slow. Please help me to diagnose the problem.

1. The result of

$ systemd-analyze critical-chain

is:

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

graphical.target @4.033s
└─sddm.service @4.033s
  └─systemd-logind.service @3.226s +801ms
    └─basic.target @3.213s
      └─sockets.target @3.213s
        └─org.cups.cupsd.socket @3.213s
          └─sysinit.target @3.207s
            └─systemd-backlight@backlight:intel_backlight.service @2.051s +1.155s
              └─system-systemd\x2dbacklight.slice @1.736s
                └─system.slice
                  └─-.slice

2. The result of

$ systemd-analyze blame

is:

7.061s NetworkManager-wait-online.service                   
1.095s systemd-backlight@backlight:intel_backlight.service  
1.015s lvm2-monitor.service                                 
 801ms systemd-logind.service                               
 704ms home.mount                                           
 513ms upower.service                                       
 477ms systemd-hostnamed.service                            
 462ms systemd-udevd.service                                
 454ms systemd-timesyncd.service                            
 380ms initrd-switch-root.service                           
 376ms systemd-journal-flush.service                        
 364ms systemd-journald.service                             
 271ms tlp.service                                          
 211ms boot.mount                                           
 170ms udisks2.service                                      
 141ms systemd-udev-trigger.service                         
 133ms systemd-modules-load.service                         
  82ms polkit.service                                       
  82ms initrd-parse-etc.service                             
  79ms modprobe@drm.service                                 
  78ms user@1000.service                                    
  72ms NetworkManager.service                               
  67ms bluetooth.service                                    
  57ms thermald.service                                     
  50ms systemd-fsck@dev-disk-by\x2duuid-CA1B\x2dF8FF.service
  47ms var-lib-systemd\x2dswap-swapfc-1.swap                
  45ms systemd-tmpfiles-setup-dev.service                   
  43ms systemd-random-seed.service                          
  40ms systemd-fsck-root.service                            
  37ms systemd-backlight@leds:dell::kbd_backlight.service   
  34ms systemd-update-utmp.service                          
  33ms org.cups.cupsd.service                               
  28ms systemd-tmpfiles-setup.service                       
  22ms user-runtime-dir@1000.service                        
  19ms dev-hugepages.mount                                  
  19ms wpa_supplicant.service                               
  19ms systemd-remount-fs.service                           
  18ms dev-mqueue.mount                                     
  18ms initrd-cleanup.service                               
  18ms systemd-rfkill.service                               
  17ms sys-kernel-debug.mount                               
  16ms sys-kernel-tracing.mount                             
  15ms systemd-user-sessions.service                        
  15ms rtkit-daemon.service                                 
  14ms tmp.mount                                            
  13ms kmod-static-nodes.service                            
  13ms systemd-sysctl.service                               
   7ms initrd-udevadm-cleanup-db.service                    
   4ms sys-kernel-config.mount         

Last edited by rabipoudel (2020-05-13 17:01:26)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,381

Re: Slow boot time into graphical.target?

Please create your own thread in the future instead of hijacking existing ones.

Nothing here is slow, you reach sddm in 4 seconds, what more do you want? Or is the problem after login?

Mod note: Split from https://bbs.archlinux.org/viewtopic.php?id=253013

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,407

Re: Slow boot time into graphical.target?

1.095s systemd-backlight@backlight:intel_backlight.service
1.015s lvm2-monitor.service

If you never change backlight from the keyboard (easy on desktops, harder on laptops) you can disable / mask systemd-backlight@backlight .
In case you don't use lvm volumes you can disable / mask lvm2-monitor.service

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,381

Re: Slow boot time into graphical.target?

Hmm I ran some of these in my own system and it seems like critical chain and blame might not provide a complete enough picture (anymore? I'm somewhat certain they used to be more telling). What's your output for just

systemd-analyze

and to check the information that is out of scope for systemd-analyze, after being logged into the "usable state" what's your

sudo journalctl -b

Last edited by V1del (2020-05-15 13:25:59)