Boot time LM20

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
tommiedepommie
Level 1
Level 1
Posts: 6
Joined: Mon Dec 17, 2018 7:07 am

Boot time LM20

Post by tommiedepommie »

Hello,

I have a B450 gaming max mainboard with an WDC 1TB M.2 and dual boot win10+LM20
The boottime for LM20 is very slow.
When I look at systemd-analyze it says:

Code: Select all

Startup finished in 34.541s (firmware) + 9.768s (loader) + 37.479s (kernel) + 15.394s (userspace) = 1min 37.183s 
graphical.target reached after 15.387s in userspace
Boottime of 1.37 min is pretty long isn't it?

grt tom
User avatar
antikythera
Level 9
Level 9
Posts: 2630
Joined: Thu Jul 02, 2020 12:52 pm

Re: Boot time LM20

Post by antikythera »

yes, very. what does the following give:

Code: Select all

systemd-analyze critical-chain
Don't take life so seriously, nobody gets out alive anyway!
AMSTRAD CPC6128 - 128KB RAM, 3" Hitachi Floppy Diskette Drive, External Sony Cassette Recorder, Locomotive BASIC 1.1, CTM-644 Monitor
tommiedepommie
Level 1
Level 1
Posts: 6
Joined: Mon Dec 17, 2018 7:07 am

Re: Boot time LM20

Post by tommiedepommie »

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.

Code: Select all

graphical.target @15.064s
└─udisks2.service @822ms +14.241s
  └─basic.target @778ms
    └─sockets.target @778ms
      └─uuidd.socket @778ms
        └─sysinit.target @776ms
          └─systemd-timesyncd.service @488ms +288ms
            └─systemd-tmpfiles-setup.service @472ms +13ms
              └─systemd-journal-flush.service @408ms +62ms
                └─systemd-journald.service @137ms +268ms
                  └─systemd-journald.socket @134ms
                    └─system.slice @131ms
                      └─-.slice @131ms
User avatar
karlchen
Level 21
Level 21
Posts: 13503
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Boot time LM20

Post by karlchen »

This part in your systemd-analyze output, 37.479s (kernel), might suggest that the system wastes 30 seconds looking for a swap device, which does not exist. Kernel loading times clearly above 10 seconds, even on old machines, usually tell that something has been misconfigured.

This looks suspicious as well: 34.541s (firmware). My machines do not even mention firmware loading times.
Hm. Maybe my machines do not have any firmware at all, all just virtual ware, software. :wink:

Code: Select all

$ systemd-analyze
Startup finished in 4.474s (kernel) + 42.049s (userspace) = 46.524s
graphical.target reached after 19.196s in userspace

Code: Select all

$ systemd-analyze blame
         22.898s apt-daily.service
          7.035s systemd-journal-flush.service
          6.647s NetworkManager-wait-online.service
          5.874s dev-mmcblk0p2.device
          4.307s systemd-udevd.service
          2.414s NetworkManager.service
          1.957s networkd-dispatcher.service
          1.885s ubuntu-system-adjustments.service
          1.726s udisks2.service
          1.626s lvm2-monitor.service
          1.525s gpu-manager.service
          1.266s ModemManager.service
          1.244s accounts-daemon.service
          1.225s ufw.service
           946ms wpa_supplicant.service
           855ms thermald.service
           769ms systemd-tmpfiles-setup.service
           644ms systemd-fsck@dev-disk-by\x2duuid-4FB8\x2d1D67.service
           612ms postfix@-.service
           595ms systemd-tmpfiles-setup-dev.service
           559ms apt-daily-upgrade.service
           535ms colord.service
           526ms dns-clean.service
           521ms grub-common.service
           514ms systemd-logind.service
           513ms avahi-daemon.service
           362ms apparmor.service
           328ms systemd-sysctl.service
           300ms boot-efi.mount
           258ms systemd-modules-load.service
           212ms rsyslog.service
           197ms polkit.service
           188ms keyboard-setup.service
           173ms networking.service
           172ms systemd-backlight@leds:dell::kbd_backlight.service
           171ms bluetooth.service
           146ms lm-sensors.service
           129ms lightdm.service
           128ms plymouth-quit-wait.service
           100ms speech-dispatcher.service
            89ms dev-disk-by\x2duuid-3923dbe2\x2d2832\x2d4b17\x2d9f2c\x2df9ae086d310c.swap
            84ms upower.service
            84ms alsa-restore.service
            73ms systemd-udev-trigger.service
            71ms systemd-journald.service
            70ms systemd-timesyncd.service
            67ms plymouth-read-write.service
            58ms packagekit.service
            46ms systemd-resolved.service
            46ms setvtrgb.service
            45ms systemd-random-seed.service
            45ms systemd-remount-fs.service
            40ms systemd-rfkill.service
            32ms blk-availability.service
            32ms sys-kernel-debug.mount
            32ms user@1000.service
            31ms kmod-static-nodes.service
            31ms dev-hugepages.mount
            27ms systemd-update-utmp.service
            18ms systemd-tmpfiles-clean.service
            14ms ureadahead-stop.service
            13ms plymouth-start.service
             8ms hddtemp.service
             7ms kerneloops.service
             4ms motd-news.service
             3ms rtkit-daemon.service
             3ms systemd-update-utmp-runlevel.service
             2ms systemd-backlight@backlight:intel_backlight.service
             2ms dev-mqueue.mount
             2ms systemd-user-sessions.service
             2ms console-setup.service
             1ms sys-kernel-config.mount
             1ms pppd-dns.service
             1ms finalrd.service
             1ms sys-fs-fuse-connections.mount
             1ms postfix.service
           748us openvpn.service

Code: Select all

$ 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 @19.196s
└─multi-user.target @19.196s
  └─postfix.service @19.195s +1ms
    └─postfix@-.service @18.581s +612ms
      └─network-online.target @18.573s
        └─NetworkManager-wait-online.service @11.925s +6.647s
          └─NetworkManager.service @9.509s +2.414s
            └─dbus.service @9.332s
              └─basic.target @9.331s
                └─sockets.target @9.331s
                  └─uuidd.socket @9.331s
                    └─sysinit.target @9.293s
                      └─systemd-timesyncd.service @9.222s +70ms
                        └─systemd-tmpfiles-setup.service @8.427s +769ms
                          └─systemd-journal-flush.service @1.391s +7.035s
                            └─systemd-remount-fs.service @1.345s +45ms
                              └─systemd-journald.socket @1.312s
                                └─system.slice @1.310s
                                  └─-.slice @1.306s
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 9.51 64-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)
Kseanfitz_1
Level 2
Level 2
Posts: 69
Joined: Mon Jun 15, 2020 2:32 pm
Location: USA love it or leave it!

Re: Boot time LM20

Post by Kseanfitz_1 »

As per another current thread Boot Log Errors "apt-daily.service" seems to take an extremely long time in your case, mine shows as,"706ms apt-daily.service >"
Also, again in your case network listings accumulate to add much time... mine as listed in the "Boot Log Errors" thread shows as, 247ms networkd-dispatcher.service >109ms networking.service >96ms NetworkManager.service >.

Just to give another output to look at for clues...

Code: Select all

graphical.target @5.561s
└─udisks2.service @929ms +4.632s <---------
  └─basic.target @894ms
    └─sockets.target @894ms
      └─uuidd.socket @894ms
        └─sysinit.target @891ms
          └─systemd-timesyncd.service @618ms +273ms <---------
            └─systemd-tmpfiles-setup.service @605ms +10ms <---------
              └─local-fs.target @600ms
                └─run-user-1000-gvfs.mount @3.022s
                  └─run-user-1000.mount @2.496s
                    └─swap.target @581ms
                      └─dev-disk-by\x2duuid-119524e6\x2d652e\x2d4d18\x2da914\x2d2e8a35580199.swap @557ms +21ms <---------
                        └─dev-disk-by\x2duuid-119524e6\x2d652e\x2d4d18\x2da914\x2d2e8a35580199.device @556ms
Added arrows indicate entries outputted in red.
Last edited by Kseanfitz_1 on Fri Jul 17, 2020 11:47 pm, edited 1 time in total.
Welcome to the Linux Mint forums!
"One, is glad to be of service."
User avatar
Joe2Shoe
Level 5
Level 5
Posts: 538
Joined: Wed Oct 18, 2017 8:12 pm
Location: Ozone

Re: Boot time LM20

Post by Joe2Shoe »

I have LM20 Cinnamon on 1 laptop and LM20 MATE on another.
On both laptops, the boot time went from 1 minute to 3 minutes, and when I click on File Manager, it takes 1 minute to open.
Intel sound went out on both laptops.
The printer no longer works on both laptops.

I fixed all those issues after much research and 40+ years hacking.
So, what's next?
If it gets worse, I'll revert back to LM19.3 via Timeshift, and wait until next year when the bugs have been squashed.
"Tolerance is the refuge of men without conviction."
"Common sense is not so common" - Voltaire
User avatar
karlchen
Level 21
Level 21
Posts: 13503
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Boot time LM20

Post by karlchen »

Hi, Kseanfitz_1.
Kseanfitz_1 wrote:
Thu Jul 16, 2020 2:05 pm
As per another current thread "apt-daily.service" seems to take an extremely long time in your case
You may safely ignore any issues, which you detect in my output. There are none. All is fine. And apt-daily.service is as slow as the low bandwidth internet connections in good old Germany permit.
This is tommiedepommie's thread and his startup times are really weird. He reports a problem (correct).

Best regards,
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 9.51 64-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)
User avatar
trytip
Level 13
Level 13
Posts: 4919
Joined: Tue Jul 05, 2016 1:20 pm

Re: Boot time LM20

Post by trytip »

dude if we don't see your WHOLE systemd-analyze blame output how can anyone help? type the command in terminal and hit enter. when you see something like lines 1-23 at the bottom it means you are on line 23 and you need to hit enter again and again until the entire output is displayed.
lines 41-63/63 (END)
Image
User avatar
karlchen
Level 21
Level 21
Posts: 13503
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Boot time LM20

Post by karlchen »

Hi, trytip.
Has the unknown dude, whom you talk to in your post, perhaps a name? Addressing him by name might make it clearer, whom you talk to. :wink:
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 9.51 64-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)
mr_raider
Level 7
Level 7
Posts: 1889
Joined: Sun Jun 20, 2010 9:50 am
Location: Montreal, QC

Re: Boot time LM20

Post by mr_raider »

Mint is very user friendly and comes with everything you need out the box. There is a price to be paid for it.

I have virtually the same hardware as you (b450 board, 1tb nvme drive):

Code: Select all

mr_raider@HK-47:~$ systemd-analyze
Startup finished in 14.817s (firmware) + 5.990s (loader) + 4.545s (kernel) + 7.000s (userspace) = 32.353s
graphical.target reached after 6.995s in userspace
Iy could be faster if I set my BIOS to fast boot.

That's another distro though.
Image
Kseanfitz_1
Level 2
Level 2
Posts: 69
Joined: Mon Jun 15, 2020 2:32 pm
Location: USA love it or leave it!

Re: Boot time LM20

Post by Kseanfitz_1 »

karlchen wrote:
Fri Jul 17, 2020 9:15 am
Hi, Kseanfitz_1.
Kseanfitz_1 wrote:
Thu Jul 16, 2020 2:05 pm
As per another current thread "apt-daily.service" seems to take an extremely long time in your case
You may safely ignore any issues, which you detect in my output. There are none. All is fine. And apt-daily.service is as slow as the low bandwidth internet connections in good old Germany permit.
This is tommiedepommie's thread and his startup times are really weird. He reports a problem (correct).

Best regards,
Karl
I have now gone and made a reference and link to the "As per another current thread" reference,
sorry for the confusion I seem to have caused, but I will say your explanation of a :wink: not so fast :wink: internet was something for me to learn from :D

Kevin
Welcome to the Linux Mint forums!
"One, is glad to be of service."
User avatar
trytip
Level 13
Level 13
Posts: 4919
Joined: Tue Jul 05, 2016 1:20 pm

Re: Boot time LM20

Post by trytip »

mr_raider wrote:
Fri Jul 17, 2020 10:50 pm
Mint is very user friendly and comes with everything you need out the box. There is a price to be paid for it.

I have virtually the same hardware as you (b450 board, 1tb nvme drive):

Code: Select all

mr_raider@HK-47:~$ systemd-analyze
Startup finished in 14.817s (firmware) + 5.990s (loader) + 4.545s (kernel) + 7.000s (userspace) = 32.353s
graphical.target reached after 6.995s in userspace

Code: Select all

mint03@mint03:~$ systemd-analyze
Startup finished in 6.229s (kernel) + 1.942s (userspace) = 8.172s
graphical.target reached after 1.937s in userspace
i have a ryzen3 with a used 256 SSD how is my start up faster? i know i masked or disabled some start up services but i don't quite remember which now.
Image
mr_raider
Level 7
Level 7
Posts: 1889
Joined: Sun Jun 20, 2010 9:50 am
Location: Montreal, QC

Re: Boot time LM20

Post by mr_raider »

trytip wrote:
Sun Jul 19, 2020 11:55 am
mr_raider wrote:
Fri Jul 17, 2020 10:50 pm
Mint is very user friendly and comes with everything you need out the box. There is a price to be paid for it.

I have virtually the same hardware as you (b450 board, 1tb nvme drive):

Code: Select all

mr_raider@HK-47:~$ systemd-analyze
Startup finished in 14.817s (firmware) + 5.990s (loader) + 4.545s (kernel) + 7.000s (userspace) = 32.353s
graphical.target reached after 6.995s in userspace

Code: Select all

mint03@mint03:~$ systemd-analyze
Startup finished in 6.229s (kernel) + 1.942s (userspace) = 8.172s
graphical.target reached after 1.937s in userspace
i have a ryzen3 with a used 256 SSD how is my start up faster? i know i masked or disabled some start up services but i don't quite remember which now.
That's excellent. As an end user, you can only change the userspace time. I checked my systemd chain and a good chunk of my time is from the virtualbox services.

My laptop on the other hand is lightning fast

Code: Select all

mr_raider@HP-ProBook-440-G5:~$ systemd-analyze
Startup finished in 8.913s (firmware) + 2.893s (loader) + 6.195s (kernel) + 1.276s (userspace) = 19.278s
graphical.target reached after 1.271s in userspace
I did some experimentation in a VM with fresh install of Mint XFCE and then Kubuntu 20.04. They have roughly the same boot time, with Mint being barely 1.5 secs slower.

So clearly the OP has room for optimization.

BTW the critical chain chart should be analayzed with caution. It can change from one boot to the next. It does not take into account several factors including services starting conurrently.

The systemd-analyze plot command produces a more useful graphic IMHO.
Image
Post Reply

Return to “Installation & Boot”