On 6/28/21 10:27 AM, Roger Heflin wrote:
Run:
systemd-analyze blame
Thanks very much Roger. I ran that and got
14.955s NetworkManager-wait-online.service
3.983s plymouth-quit-wait.service
1.726s systemd-udev-settle.service
1.128s fwupd.service
(and so on ....)
It seems to be that the NetworkM..service is taking quite a bit of time.
As Chris pointed out.
Find one of the last critical services that indicates the machine is "up".
systemd-analyze critical-chain <name> (this will show you what took
how long prior to that service)
I did this on on the NetworkM...service and got:
NetworkManager-wait-online.service +14.955s
└─NetworkManager.service @1.841s +26ms
└─network-pre.target @1.839s
└─firewalld.service @1.241s +597ms
└─polkit.service @1.417s +122ms
└─basic.target @1.235s
└─dbus-broker.service @1.278s +54ms
└─dbus.socket @1.229s
└─sysinit.target @1.225s
└─systemd-userdbd.service @16.936s +22ms
└─systemd-userdbd.socket @368ms
└─system.slice
└─-.slice
at 18seconds it looks like your network and the graphics drivers are
getting loaded, so all before this is initing the system, but all
"kernel" drivers were loaded at 8 sec so it seems from 8 sec -> 18 sec
the userspace pieces are being started, but those pieces do not load
any kernel pieces so they do not show the work happening in userspace.
If you look at messages file it likely has a lot of userspace pieces
starting up.
Thanks for educating me. I don't know what you mean by the "messages
file" here though.
Thank you.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
