Slower boot up

SolydXK is too quiet for you? SolydXK Enthusiast Editions, based on Debian Testing is for you! Here you can find news about Debian Testing and Unstable too, and also tests on SolydXK programs.
The support for SolydXK EE is provided by the community.
User avatar
xendistar
Posts: 515
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Slower boot up

Postby xendistar » 31 May 2020 10:14

Since an update earlier in the week, my bootup has been a couple of second slower.

The laptop will boots it way through to the acpi screen as normal and then the SolydX wallpaper popups, now prior to the update the wallpaper would flash on screen and then disappear, but since that update, it sits there for about 2-3 seconds and then continues to boot. When this pause happens there is no disk activity, the disk light goes off then after a couple of seconds it will start to flash and the laptop continues to boot. I have not noticed any other issue.

Laptop is a Lenonvo T530 with SolydX EE

This is the update that started the issue:

Code: Select all

Start-Date: 2020-05-28  22:07:18
Commandline: apt-get dist-upgrade
Requested-By: mit (1000)
Upgrade: enchant:amd64 (1.6.0-11.3, 1.6.0-11.4), apt:amd64 (2.1.4, 2.1.5), printer-driver-foo2zjs:amd64 (20171202dfsg0-4, 20200505dfsg0-1), solydx-system-adjustments-11:amd64 (3.2.8, 3.2.9), libapt-pkg6.0:amd64 (2.1.4, 2.1.5), libenchant1c2a:amd64 (1.6.0-11.3, 1.6.0-11.4), apt-utils:amd64 (2.1.4, 2.1.5), printer-driver-foo2zjs-common:amd64 (20171202dfsg0-4, 20200505dfsg0-1)
End-Date: 2020-05-28  22:07:59
I not after the fastest bootup, but I am able to point to a point and say me system changed after this update, might help somebody else

User avatar
ilu
Posts: 2680
Joined: 09 Oct 2013 12:45

Re: Slower boot up

Postby ilu » 31 May 2020 13:51

Post the output of systemd-analyze blame and systemd-analyze critical-chain.

User avatar
xendistar
Posts: 515
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: Slower boot up

Postby xendistar » 31 May 2020 14:36

OK is is the Output

In the systemd-analyze critical-chain the line that were shown in Red I have marked at the end of the line like "(IN RED)"

Code: Select all

mit@telstar:~$ systemd-analyze blame
7.674s NetworkManager-wait-online.service                                      >
5.548s apt-daily.service                                                       >
1.468s solydxk-system-adjust.service                                           >
 808ms ufw.service                                                             >
 804ms apt-daily-upgrade.service                                               >
 643ms upower.service                                                          >
 640ms systemd-logind.service                                                  >
 571ms systemd-journal-flush.service                                           >
 564ms dev-sda1.device                                                         >
 455ms media-nas.mount                                                         >
 452ms udisks2.service                                                         >
 431ms systemd-journald.service                                                >
 194ms accounts-daemon.service                                                 >
 166ms bluetooth.service                                                       >
 162ms polkit.service                                                          >
 162ms NetworkManager.service                                                  >
 161ms loadcpufreq.service                                                     >
 152ms apparmor.service                                                        >
 146ms rtkit-daemon.service                                                    >
 139ms wpa_supplicant.service                                                  >
 137ms smartmontools.service                                                   >
 111ms networking.service                                                      >
 107ms user@1000.service                                                       >
 105ms nmbd.service                                                            >
  98ms smbd.service                                                            >
  96ms lightdm.service                                                         >
  93ms ModemManager.service                                                    >
  92ms plymouth-quit-wait.service                                              >
  89ms rsyslog.service                                                         >
  77ms systemd-udev-trigger.service                                            >
  77ms systemd-udevd.service                                                   >
  76ms e2scrub_reap.service                                                    >
  65ms systemd-fsck@dev-disk-by\x2duuid-d64288f3\x2d289b\x2d4534\x2dab45\x2d4bd>
  60ms systemd-backlight@backlight:intel_backlight.service                     >
  59ms plymouth-start.service                                                  >
  55ms colord.service                                                          >
  47ms dev-disk-by\x2duuid-2aec0ea2\x2df9e1\x2d4c8f\x2db9e1\x2db9d7ce929b10.swa>
  40ms ntp.service                                                             >
  35ms run-rpc_pipefs.mount                                                    >
  33ms alsa-restore.service                                                    >
  33ms lm-sensors.service                                                      >
  32ms home.mount                                                              >
  32ms fwupd-refresh.service                                                   >
  30ms systemd-backlight@backlight:nv_backlight.service                        >
  30ms systemd-modules-load.service                                            >
  28ms systemd-rfkill.service                                                  >
  24ms lpd.service                                                             >
  21ms binfmt-support.service                                                  >
  20ms cpufrequtils.service                                                    >
  19ms hddtemp.service                                                         >
  17ms systemd-tmpfiles-setup-dev.service                                      >
  16ms systemd-sysusers.service                                                >
  16ms minissdpd.service                                                       >
  16ms dev-hugepages.mount                                                     >
  16ms tmp.mount                                                               >
  16ms plymouth-read-write.service                                             >
  16ms systemd-tmpfiles-setup.service                                          >
  16ms dev-mqueue.mount                                                        >
  16ms systemd-tmpfiles-clean.service                                          >
  15ms rpcbind.service                                                         >
  14ms var-backups.mount                                                       >
  14ms systemd-remount-fs.service                                              >
  14ms sys-kernel-debug.mount                                                  >
  14ms systemd-random-seed.service                                             >
  14ms pppd-dns.service                                                        >
  13ms sys-kernel-tracing.mount                                                >
  13ms systemd-update-utmp.service                                             >
  12ms keyboard-setup.service                                                  >
  12ms kmod-static-nodes.service                                               >
  11ms var-log-ConsoleKit.mount                                                >
  11ms systemd-sysctl.service                                                  >
  10ms systemd-update-utmp-runlevel.service                                    >
   9ms user-runtime-dir@1000.service                                           >
   9ms systemd-user-sessions.service                                           >
   9ms var-log-clamav.mount                                                    >
   8ms systemd-backlight@leds:tpacpi::kbd_backlight.service                    >
   8ms proc-sys-fs-binfmt_misc.mount                                           >
   7ms atd.service                                                             >
   7ms console-setup.service                                                   >
   7ms nfs-config.service                                                      >
   6ms var-log-cups.mount                                                      >
   6ms sys-fs-fuse-connections.mount                                           >
   6ms openvpn.service                                                         >
   5ms var-tmp.mount                                                           >
   4ms e2scrub_all.service                                                     >
   4ms ifupdown-pre.service                                                    >
lines 64-86/86 (END)



mit@telstar:~$ systemd-analyze critical-chain
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 @10.187s
└─multi-user.target @10.187s
  └─cpufrequtils.service @10.166s +20ms ( IN RED)
    └─loadcpufreq.service @10.001s +161ms ( IN RED)
      └─remote-fs.target @9.995s
        └─media-nas.mount @9.538s +455ms ( IN RED)
          └─network-online.target @9.535s
            └─NetworkManager-wait-online.service @1.859s +7.674s ( IN RED)
              └─NetworkManager.service @1.696s +162ms ( IN RED)
                └─dbus.service @1.693s
                  └─basic.target @1.682s
                    └─sockets.target @1.682s
                      └─uuidd.socket @1.681s
                        └─sysinit.target @1.677s
                          └─haveged.service @1.676s
                            └─apparmor.service @1.522s +152ms ( IN RED)
                              └─local-fs.target @1.520s
                                └─home.mount @983ms +32ms ( IN RED) 
                                  └─systemd-fsck@dev-disk-by\x2duuid-d64288f3\x>( IN RED)
                                    └─dev-disk-by\x2duuid-d64288f3\x2d289b\x2d4>

User avatar
ilu
Posts: 2680
Joined: 09 Oct 2013 12:45

Re: Slower boot up

Postby ilu » 31 May 2020 14:39

Now wait for somebody who is actually running EE. :D

User avatar
troypulk
Posts: 192
Joined: 20 Jul 2014 22:43
Location: Washington State, USA

Re: Slower boot up

Postby troypulk » 31 May 2020 15:51

Here you go, I hope you find a match.

EDIT: Sorry, I didn't realized you were on a laptop so I redid this on my laptop - HP Pavilion g7 Notebook

Code: Select all

~$ systemd-analyze blame
33.225s solydxk-system-adjust.service                                                            
10.741s nmbd.service                                                                             
 8.868s NetworkManager-wait-online.service                                                       
 7.895s udisks2.service                                                                          
 6.281s dev-sda2.device                                                                          
 5.572s accounts-daemon.service                                                                  
 5.158s smbd.service                                                                             
 4.615s ModemManager.service                                                                     
 4.445s NetworkManager.service                                                                   
 4.414s polkit.service                                                                           
 4.404s iio-sensor-proxy.service                                                                 
 4.349s rtkit-daemon.service                                                                     
 4.312s systemd-logind.service                                                                   
 4.311s wpa_supplicant.service                                                                   
 2.470s loadcpufreq.service                                                                      
 2.341s lightdm.service                                                                          
 2.330s plymouth-quit-wait.service                                                               
 2.143s e2scrub_reap.service                                                                     
 2.080s networking.service                                                                       
 1.971s systemd-journal-flush.service                                                            
 1.878s colord.service                                                                           
 1.835s apparmor.service                                                                         
 1.729s systemd-udevd.service                                                                    
 1.576s upower.service                                                                           
 1.331s rsyslog.service                                                                          
 1.203s ntp.service                                                                              
 1.114s xl2tpd.service                                                                           
  943ms systemd-journald.service                                                                 
  895ms systemd-modules-load.service                                                             
  847ms systemd-sysusers.service                                                                 
  682ms lpd.service                                                                              
  660ms systemd-random-seed.service                                                              
  653ms systemd-tmpfiles-setup.service                                                           
  632ms minissdpd.service                                                                        
  628ms avahi-daemon.service                                                                     
  523ms rpcbind.service                                                                          
  505ms lm-sensors.service                                                                       
  447ms blueman-mechanism.service                                                                
  416ms systemd-fsck@dev-disk-by\x2duuid-7c17214d\x2d71c4\x2d4aee\x2d8555\x2db2083cdc6e40.service
  395ms systemd-tmpfiles-setup-dev.service                                                       
  368ms run-rpc_pipefs.mount                                                                     
  348ms systemd-udev-trigger.service                                                             
  338ms ifupdown-pre.service                                                                     
  318ms binfmt-support.service                                                                   
  288ms systemd-backlight@backlight:radeon_bl0.service                                           
  279ms atd.service                                                                              
  256ms console-setup.service                                                                    
  245ms ufw.service                                                                              
  243ms cpufrequtils.service                                                                     
  232ms pppd-dns.service                                                                         
  217ms alsa-restore.service                                                                     
  213ms keyboard-setup.service                                                                   
  212ms user@1000.service                                                                        
  202ms systemd-rfkill.service                                                                   
  181ms nfs-config.service                                                                       
  162ms dev-disk-by\x2duuid-ccda7244\x2d2047\x2d426c\x2d9a82\x2d4e55555a0c72.swap                
  152ms plymouth-read-write.service                                                              
  143ms systemd-sysctl.service                                                                   
  121ms home.mount                                                                               
  120ms plymouth-start.service                                                                   
  111ms hddtemp.service                                                                          
  100ms dev-hugepages.mount                                                                      
  100ms dev-mqueue.mount                                                                         
   98ms sys-kernel-debug.mount                                                                   
   96ms sys-kernel-tracing.mount                                                                 
   93ms kmod-static-nodes.service                                                                
   92ms systemd-user-sessions.service                                                            
   89ms proc-sys-fs-binfmt_misc.mount                                                            
   80ms systemd-remount-fs.service                                                               
   54ms systemd-update-utmp.service                                                              
   29ms user-runtime-dir@1000.service                                                            
   17ms systemd-update-utmp-runlevel.service                                                     
   16ms openvpn.service

~$ systemd-analyze critical-chain
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 @49.934s
└─multi-user.target @49.934s
  └─smbd.service @36.407s +5.158s
    └─nmbd.service @25.660s +10.741s
      └─network-online.target @25.562s
        └─NetworkManager-wait-online.service @16.693s +8.868s
          └─NetworkManager.service @12.244s +4.445s
            └─dbus.service @12.234s
              └─basic.target @12.121s
                └─sockets.target @12.121s
                  └─uuidd.socket @12.121s
                    └─sysinit.target @12.086s
                      └─haveged.service @12.086s
                        └─apparmor.service @10.244s +1.835s
                          └─local-fs.target @10.243s
                            └─home.mount @10.121s +121ms
                              └─systemd-fsck@dev-disk-by\x2duuid-7c17214d\x2d71c4\x2d4aee\x2d8555\x2db2083cdc6e40.>
                                └─dev-disk-by\x2duuid-7c17214d\x2d71c4\x2d4aee\x2d8555\x2db2083cdc6e40.device @9.6>


SolydX 10, 4.19.0-9 / Debian 10, 4.19.118-2 (64-bit) / Xfce 4.12.4 (64-bit)

User avatar
xendistar
Posts: 515
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: Slower boot up

Postby xendistar » 31 May 2020 16:01

I think I should point out that the laptop has a 240GB SSD drive as opposed to a conventional spinney one

User avatar
troypulk
Posts: 192
Joined: 20 Jul 2014 22:43
Location: Washington State, USA

Re: Slower boot up

Postby troypulk » 31 May 2020 16:09

Yeah, I think mine is a regular HHD.


SolydX 10, 4.19.0-9 / Debian 10, 4.19.118-2 (64-bit) / Xfce 4.12.4 (64-bit)

kurotsugi
Posts: 2268
Joined: 09 Jan 2014 00:17

Re: Slower boot up

Postby kurotsugi » 02 Jun 2020 01:31

I think it's an old bug related with network services. the system wait until the net connection is active. nothing is wrong with the system

Code: Select all

33.225s solydxk-system-adjust.service                                                            
10.741s nmbd.service                                                                             
 8.868s NetworkManager-wait-online.service    [code]
this one is also same. 
[code]7.674s NetworkManager-wait-online.service                                      >
5.548s apt-daily.service                                                       >
1.468s solydxk-system-adjust.service                                           >
as we can see here, the main culprit is network services

Code: Select all

media-nas.mount @9.538s +455ms ( IN RED)
          └─network-online.target @9.535s
            └─NetworkManager-wait-online.service @1.859s +7.674s ( IN RED)
              └─NetworkManager.service @1.696s +162ms ( IN RED)
those red stuff means that the services makes the boot process takes longer time


Return to “Testing Zone”

Who is online

Users browsing this forum: Arjen Balfoort and 2 guests