Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Slow boot

Linux Kernel, Network, and Services configuration.
Message
Author
dragonball
Posts: 33
Joined: 2014-03-27 12:37

Slow boot

#1 Post by dragonball »

Hi. I installed Debian Buster (testing) on my desktop. I have a few things here and there and I need some help to fix them. The biggest is my boot process. Is too slow. Takes too long until login screen (gdm3). Any help would be appreciated

Code: Select all

george@Debian:~$ uname -r
4.19.0-5-amd64

Code: Select all

george@Debian:~$ systemd-analyze
Startup finished in 15.736s (firmware) + 3.573s (loader) + 1min 32.412s (kernel) + 6.114s (userspace) = 1min 57.836s 
graphical.target reached after 6.108s in userspace

Code: Select all

george@Debian:~$ systemd-analyze blame
          5.115s plymouth-quit-wait.service
           885ms nvidia-persistenced.service
           354ms fwupd.service
           351ms systemd-journald.service
           342ms systemd-timesyncd.service
           282ms systemd-modules-load.service
           268ms dev-nvme0n1p2.device
           184ms systemd-logind.service
           175ms upower.service
           145ms bolt.service
           131ms geoclue.service
           102ms udisks2.service
            91ms ModemManager.service
            73ms cpufreqd.service
            67ms user@117.service
            64ms accounts-daemon.service
            62ms keyboard-setup.service
            60ms systemd-udevd.service
            54ms systemd-udev-trigger.service
            49ms lm-sensors.service
            49ms systemd-fsck@dev-disk-by\x2duuid-730e2cef\x2dd37c\x2d4b1d\x2db8
            48ms NetworkManager.service
            41ms wpa_supplicant.service
            40ms systemd-fsck@dev-disk-by\x2duuid-ED9D\x2d765B.service
            38ms user@1000.service
            37ms ssh.service
            35ms rsyslog.service
            28ms apparmor.service
            25ms gdm.service
            20ms plymouth-start.service
            20ms colord.service
            19ms systemd-tmpfiles-clean.service
            18ms polkit.service
            18ms systemd-sysctl.service
            17ms networking.service
            17ms alsa-restore.service
            16ms systemd-tmpfiles-setup.service
            14ms switcheroo-control.service
            13ms boot-efi.mount
            13ms hddtemp.service
            12ms systemd-journal-flush.service
            11ms plymouth-read-write.service
            10ms systemd-sysusers.service
            10ms dev-disk-by\x2duuid-232ad5c1\x2da2f4\x2d4193\x2d9a3f\x2dec9b59d
             8ms home.mount
             8ms pppd-dns.service
             8ms systemd-user-sessions.service
             7ms systemd-tmpfiles-setup-dev.service
             7ms user-runtime-dir@1000.service
             6ms systemd-remount-fs.service
             6ms dev-mqueue.mount
             6ms user-runtime-dir@117.service
             5ms systemd-update-utmp.service
             4ms systemd-random-seed.service
             4ms systemd-update-utmp-runlevel.service
             4ms kmod-static-nodes.service
             3ms avahi-daemon.service
             3ms dev-hugepages.mount
             3ms ifupdown-pre.service
             3ms rtkit-daemon.service
             2ms console-setup.service
             2ms sys-fs-fuse-connections.mount
             1ms sys-kernel-debug.mount

Code: Select all

george@Debian:~$ inxi -F
System:
  Host: Debian Kernel: 4.19.0-5-amd64 x86_64 bits: 64 Desktop: Gnome 3.30.2 
  Distro: Debian GNU/Linux bullseye/sid 
Machine:
  Type: Desktop Mobo: ASUSTeK model: P10S-I Series v: Rev 1.xx 
  serial: 180527654500220 UEFI: American Megatrends v: 4401 date: 03/05/2018 
CPU:
  Topology: Quad Core model: Intel Xeon E3-1270 v6 bits: 64 type: MT MCP 
  L2 cache: 8192 KiB 
  Speed: 4100 MHz max: 4200 MHz Core speeds (MHz): 1: 4177 2: 4091 3: 4064 
  4: 4148 5: 4102 6: 4100 7: 4125 8: 4155 
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nvidia v: 418.74 
  Display: server: X.Org 1.20.4 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1200~60Hz 
  OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 
Audio:
  Device-1: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel 
  Sound Server: ALSA v: k4.19.0-5-amd64 
Network:
  Device-1: Intel I210 Gigabit Network driver: igb 
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 4c:ed:fb:91:92:79 
  Device-2: Intel I210 Gigabit Network driver: igb 
  IF: rename3 state: up speed: 1000 Mbps duplex: full mac: 4c:ed:fb:91:92:7a 
Drives:
  Local Storage: total: 223.57 GiB used: 23.05 GiB (10.3%) 
  ID-1: /dev/nvme0n1 vendor: Toshiba model: RC100 size: 223.57 GiB 
Partition:
  ID-1: / size: 27.38 GiB used: 9.35 GiB (34.1%) fs: ext4 
  dev: /dev/nvme0n1p2 
  ID-2: /home size: 175.38 GiB used: 13.70 GiB (7.8%) fs: ext4 
  dev: /dev/nvme0n1p4 
  ID-3: swap-1 size: 15.93 GiB used: 0 KiB (0.0%) fs: swap 
  dev: /dev/nvme0n1p3 
Sensors:
  System Temperatures: cpu: 50.0 C mobo: 29.8 C gpu: nvidia temp: 43 C 
  Fan Speeds (RPM): cpu: 0 fan-2: 928 fan-3: 0 fan-4: 1421 fan-5: 1433 
  fan-6: 0 gpu: nvidia fan: 42% 
Info:
  Processes: 231 Uptime: 1h 20m Memory: 15.60 GiB used: 2.89 GiB (18.6%) 
  Shell: bash inxi: 3.0.35 

L_V
Posts: 1477
Joined: 2007-03-19 09:04
Been thanked: 11 times

Re: Slow boot

#2 Post by L_V »

dragonball wrote:Hi. I installed Debian Buster (testing)
Buster is STABLE now ! Testing name is Bullseye.
If you are looking for a fast boot, plymouth is probably not necessary.

systemd-analyze : 5s on SSD / with kde desktop manager / light install

Code: Select all

Startup finished in 3.454s (kernel) + 2.100s (userspace) = 5.555s 
graphical.target reached after 2.024s in userspace
systemd-analyze blame

Code: Select all

           901ms dev-sda3.device
           314ms NetworkManager.service
           248ms user@1000.service
           241ms udisks2.service
           196ms systemd-logind.service
           150ms lm-sensors.service
           146ms systemd-fsck@dev-disk-by\x2duuid-423fd594\x2d9412\x2d4a40\x2da9c8\x2d37f40665498c.service
           137ms systemd-udev-trigger.service
           135ms systemd-fsck@dev-disk-by\x2duuid-70539b5f\x2d7144\x2d4935\x2d8ed5\x2d33e0499828eb.service
           131ms systemd-timesyncd.service
           131ms networking.service
           126ms systemd-journald.service
            .../...

dragonball
Posts: 33
Joined: 2014-03-27 12:37

Re: Slow boot

#3 Post by dragonball »

I disable plymouth using this command

Code: Select all

 sudo systemctl disable plymouth-start
I also removed from grub.cfg quiet parameter and updated grub using

Code: Select all

sudo update-grub
Rebooting still have the problem. My Boot process waits over 15 sec on this point before go further

Image

L_V
Posts: 1477
Joined: 2007-03-19 09:04
Been thanked: 11 times

Re: Slow boot

#4 Post by L_V »

" Startup finished in 15.736s (firmware) "

You need to investigate with journalctl or dmesg what happen with your firmware (one probably missing, or wrong one ?)

dragonball
Posts: 33
Joined: 2014-03-27 12:37

Re: Slow boot

#5 Post by dragonball »

This is my dmesg: https://pastebin.com/Utx9Bsch but I think, I don't see something suspicious.
Also this is my journalctl: https://pastebin.com/g5cyfSbG which is chaos! :P

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: Slow boot

#6 Post by sunrat »

Nobody is going to read your whole journal. Filter it to just show errors:

Code: Select all

journalctl -b -p3
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

dragonball
Posts: 33
Joined: 2014-03-27 12:37

Re: Slow boot

#7 Post by dragonball »

I guess you have right. Even me, i felt tired just look at it!

My

Code: Select all

journalctl -b -p3
returns no error?

Code: Select all

george@Debian:~$ sudo  journalctl -b -p3
[sudo] password for george: 
-- Logs begin at Sat 2019-07-27 13:50:36 EEST, end at Sat 2019-07-27 15:12:52 EEST. --
-- No entries --

L_V
Posts: 1477
Joined: 2007-03-19 09:04
Been thanked: 11 times

Re: Slow boot

#8 Post by L_V »

Concerning plymouth, a bit surprised how it seems now so easy to "disable" plymouth.
Is is really "disabled" ? Or not visible at boot...
If not "removed", Plymouth is still part of initrd.

Can you install initramfs-tools-core , and check this:

Code: Select all

lsinitramfs /initrd.img | grep -i plymouth
dpkg -l | grep plymouth
For info, I don't have any plymouth in my system, never install it.
Last edited by L_V on 2019-07-27 11:51, edited 3 times in total.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Slow boot

#9 Post by Head_on_a_Stick »

dragonball wrote:My Boot process waits over 15 sec on this point before go further
Does it go any faster if you wiggle the mouse or press random keys? Could be an entropy issue. And please replace your oversized image with a link, we have forum users with limited bandwidth.

Perhaps a graphical view will give you some clues:

Code: Select all

systemd-analyze plot > boot.svg
Also your kernel seems to take far too long, are you applying any unusual kernel parameters?

Code: Select all

cat /proc/cmdline
And yes, just disabling Plymouth would cause errors from the initramfs. Removing the package is probably better (if you don't want it).
deadbang

dragonball
Posts: 33
Joined: 2014-03-27 12:37

Re: Slow boot

#10 Post by dragonball »

Code: Select all

george@Debian:~$ lsinitramfs /initrd.img | grep -i plymouth
etc/plymouth
etc/plymouth/plymouthd.conf
scripts/init-bottom/plymouth
scripts/init-premount/plymouth
scripts/panic/plymouth
usr/bin/plymouth
usr/lib/x86_64-linux-gnu/plymouth
usr/lib/x86_64-linux-gnu/plymouth/details.so
usr/lib/x86_64-linux-gnu/plymouth/label.so
usr/lib/x86_64-linux-gnu/plymouth/renderers
usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so
usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so
usr/lib/x86_64-linux-gnu/plymouth/script.so
usr/lib/x86_64-linux-gnu/plymouth/text.so
usr/sbin/plymouthd
usr/share/plymouth
usr/share/plymouth/debian-logo.png
usr/share/plymouth/plymouthd.defaults
usr/share/plymouth/themes
usr/share/plymouth/themes/details
usr/share/plymouth/themes/details/details.plymouth
usr/share/plymouth/themes/futureprototype
usr/share/plymouth/themes/futureprototype/debian.png
usr/share/plymouth/themes/futureprototype/futureprototype.plymouth
usr/share/plymouth/themes/futureprototype/futureprototype.script
usr/share/plymouth/themes/futureprototype/logo.png
usr/share/plymouth/themes/futureprototype/logo_circle.png
usr/share/plymouth/themes/futureprototype/password_dot.png
usr/share/plymouth/themes/futureprototype/password_dot16.png
usr/share/plymouth/themes/futureprototype/password_field.png
usr/share/plymouth/themes/futureprototype/password_field16.png
usr/share/plymouth/themes/futureprototype/plymouth_background_future.png
usr/share/plymouth/themes/text
usr/share/plymouth/themes/text/text.plymouth

Code: Select all

george@Debian:~$ dpkg -l | grep plymouth
ii  libplymouth4:amd64                    0.9.4-1.1                       amd64        graphical boot animation and logger - shared libraries
ii  plymouth                              0.9.4-1.1                       amd64        boot animation, logger and I/O multiplexer
ii  plymouth-label                        0.9.4-1.1                       amd64        boot animation, logger and I/O multiplexer - label control

Code: Select all

george@Debian:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=UUID=7fa1da99-1e20-40f2-a5fb-de12ceb5ede5 ro
Just remove plymouth packages?

L_V
Posts: 1477
Joined: 2007-03-19 09:04
Been thanked: 11 times

Re: Slow boot

#11 Post by L_V »

dragonball wrote:[Just remove plymouth packages?
I did not play at plymouth for years
Why do you need a splash screen for a 5s boot....
Removing plymouth is not enough... It has also to be removed from initrd

Code: Select all

update-initramfs -u
It is easier to not install plymouth than to remove it (I remember some crazy dependency problem on some distributions....).
You can try. If you cannot, just reinstall it.

dragonball
Posts: 33
Joined: 2014-03-27 12:37

Re: Slow boot

#12 Post by dragonball »

I completely removed plymouth packages and updated initramfs buts problems is still there

Code: Select all

lsinitramfs /initrd.img | grep -i plymouth
and

Code: Select all

dpkg -l | grep plymouth
now returns nothing

L_V
Posts: 1477
Joined: 2007-03-19 09:04
Been thanked: 11 times

Re: Slow boot

#13 Post by L_V »

Do you still have this ?

Code: Select all

$ systemd-analyze blame
          5.115s plymouth-quit-wait.service

dragonball
Posts: 33
Joined: 2014-03-27 12:37

Re: Slow boot

#14 Post by dragonball »

Not anymore. So I guess is not plymouth the problem?

Code: Select all

george@Debian:~$ systemd-analyze blame
           878ms nvidia-persistenced.service
           395ms systemd-timesyncd.service
           326ms systemd-modules-load.service
           322ms systemd-journald.service
           283ms fwupd.service
           248ms dev-nvme0n1p2.device
           198ms ModemManager.service
           187ms upower.service
           166ms systemd-logind.service
           109ms bolt.service
           108ms geoclue.service
            87ms udisks2.service
            72ms user@117.service
            62ms accounts-daemon.service
            58ms systemd-udevd.service
            56ms systemd-fsck@dev-disk-by\x2duuid-730e2cef\x2dd37c\x2d4b1d\x2db8
            56ms boot-efi.mount
            52ms keyboard-setup.service
            52ms cpufreqd.service
            48ms NetworkManager.service
            47ms systemd-udev-trigger.service
            40ms user@1000.service
            37ms wpa_supplicant.service
            37ms apparmor.service
            31ms systemd-journal-flush.service
            28ms ssh.service
            26ms lm-sensors.service
            24ms systemd-fsck@dev-disk-by\x2duuid-ED9D\x2d765B.service
            23ms rsyslog.service
            22ms dev-disk-by\x2duuid-232ad5c1\x2da2f4\x2d4193\x2d9a3f\x2dec9b59d
            22ms pppd-dns.service
            22ms gdm.service
            21ms home.mount
            19ms systemd-tmpfiles-setup.service
            19ms colord.service
            18ms systemd-tmpfiles-clean.service
            14ms polkit.service
            14ms dev-hugepages.mount
            14ms networking.service
            14ms switcheroo-control.service
            13ms dev-mqueue.mount
            11ms hddtemp.service
            11ms systemd-remount-fs.service
             9ms systemd-user-sessions.service
             9ms systemd-sysctl.service
             8ms ifupdown-pre.service
             8ms sys-kernel-debug.mount
             8ms user-runtime-dir@1000.service
             8ms systemd-sysusers.service
             7ms systemd-tmpfiles-setup-dev.service
             7ms user-runtime-dir@117.service
             6ms kmod-static-nodes.service
             6ms systemd-update-utmp.service
             5ms systemd-random-seed.service
             4ms systemd-update-utmp-runlevel.service
             4ms alsa-restore.service
             3ms console-setup.service
             3ms avahi-daemon.service
             2ms rtkit-daemon.service
             2ms sys-fs-fuse-connections.mount

L_V
Posts: 1477
Joined: 2007-03-19 09:04
Been thanked: 11 times

Re: Slow boot

#15 Post by L_V »

Then some progress no ? Be positive !
Now... Nvidia. I'm not familiar with, but hope you install the right driver.
Issues with Debian Buster and nVidia drivers

+ look at your systemd-service, and compare with mine (see above).

dragonball
Posts: 33
Joined: 2014-03-27 12:37

Re: Slow boot

#16 Post by dragonball »

Seems to work right on me

Code: Select all

george@Debian:~$  glxinfo | grep renderer
OpenGL renderer string: GeForce GTX 1050 Ti/PCIe/SSE2

Code: Select all

george@Debian:~$ inxi -G
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nvidia v: 418.74 
  Display: x11 server: X.Org 1.20.4 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1200~60Hz 
  OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 

L_V
Posts: 1477
Joined: 2007-03-19 09:04
Been thanked: 11 times

Re: Slow boot

#17 Post by L_V »

And now, what says systemd-analyze ?

dragonball
Posts: 33
Joined: 2014-03-27 12:37

Re: Slow boot

#18 Post by dragonball »

Code: Select all

Startup finished in 15.737s (firmware) + 3.225s (loader) + 1min 32.044s (kernel) + 5.365s (userspace) = 1min 56.373s 
graphical.target reached after 1.818s in userspace

L_V
Posts: 1477
Joined: 2007-03-19 09:04
Been thanked: 11 times

Re: Slow boot

#19 Post by L_V »

And this:

Code: Select all

systemd-analyze critical-chain

graphical.target @2.007s
└─multi-user.target @2.006s
  └─ssh.service @1.903s +102ms
    └─network.target @1.897s
      └─NetworkManager.service @1.582s +314ms
        └─dbus.service @1.576s
          └─basic.target @1.563s
            └─sockets.target @1.563s
              └─dbus.socket @1.563s
                └─sysinit.target @1.563s
                  └─systemd-timesyncd.service @1.405s +157ms
                    └─systemd-tmpfiles-setup.service @1.350s +43ms
                      └─local-fs.target @1.346s
                        └─home.mount @1.312s +33ms
+ is this returning something

Code: Select all

dmesg | grep SSS
(as root)
+ may be systemd-bootchart can add value to the analysis
http://www.bootchart.org/images/bootchart.png

or this

Code: Select all

systemd-analyze plot > plot.svg

dragonball
Posts: 33
Joined: 2014-03-27 12:37

Re: Slow boot

#20 Post by dragonball »

Good Morning. Today I made a clean install. I kept Debian stable this time. I removed plymouth and I checked that is really removed. I also noticed that the same behavior exist with nouveau driver, before even install nvidia drivers.

My systemd-analyze doesn't change a lot :P

Code: Select all

Startup finished in 15.747s (firmware) + 5.497s (loader) + 1min 32.002s (kernel) + 4.961s (userspace) = 1min 58.208s 
graphical.target reached after 4.806s in userspace

Code: Select all

george@Debian:~$ 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 @4.806s
└─multi-user.target @4.806s
  └─hddtemp.service @4.800s +6ms
    └─network-online.target @4.799s
      └─NetworkManager-wait-online.service @815ms +3.983s
        └─NetworkManager.service @778ms +36ms
          └─dbus.service @776ms
            └─basic.target @766ms
              └─sockets.target @766ms
                └─dbus.socket @765ms
                  └─sysinit.target @764ms
                    └─systemd-timesyncd.service @494ms +269ms
                      └─systemd-tmpfiles-setup.service @477ms +15ms
                        └─local-fs.target @476ms
                          └─run-user-117.mount @917ms
                            └─swap.target @429ms
                              └─dev-disk-by\x2duuid-b7a13c9a\x2d25f6\x2d4dc7\x2d900e\x2d8ac89e98578a.swap @410ms +18ms
                                └─dev-disk-by\x2duuid-b7a13c9a\x2d25f6\x2d4dc7\x2d900e\x2d8ac89e98578a.device @369ms
And

Code: Select all

sudo dmesg | grep SSS
returns nothing

Also do I really need hddtemp.service on nvme ssd disk?

Post Reply