Slow initialization of something during boot
আনন্দ কুমার সমাদ্দার Ananda Samaddar
asamaddar at myopera.com
Tue Aug 13 17:51:16 UTC 2013
On Tue, 13 Aug 2013 12:49:13 -0400
Frank <beacon at videotron.ca> wrote:
> Since I made the switch to a 64 bit machine (still using 32 bit
> Fedora 19) there is a long delay just before lightdm comes up with
> the login screen.
> Can someone take a look at this output and perhaps point out why and
> where it's occurring ? By the way I don't use LVM or raid...can I
> disable these services? What;s the best way to do that. Even so the
> time they take doesn't account for the 6-7 second delay after booting
> before lightdm comes up.
>
> Thanks for any help
>
>
> [frank at localhost ~]$ sudo systemd-analyze blame
> 19.698s NetworkManager.service
> 19.597s accounts-daemon.service
> 18.723s chronyd.service
> 18.567s lightdm.service
> 2.406s lvm2-monitor.service
> 2.317s dmraid-activation.service
> 1.487s systemd-udev-settle.service
> 1.467s systemd-tmpfiles-setup-dev.service
> 1.152s fedora-loadmodules.service
> 1.074s systemd-fsck-root.service
> 706ms polkit.service
> 656ms systemd-sysctl.service
> 581ms fedora-readonly.service
> 537ms systemd-logind.service
> 510ms sys-kernel-debug.mount
> 508ms dev-mqueue.mount
> 508ms rtkit-daemon.service
> 505ms dev-hugepages.mount
> 500ms media-debian.mount
> 485ms tmp.mount
> 353ms systemd-udev-trigger.service
> 294ms plymouth-start.service
> 265ms systemd-readahead-replay.service
> 243ms lvm2-lvmetad.service
> 216ms systemd-random-seed-load.service
> 165ms sys-kernel-config.mount
> 156ms systemd-readahead-collect.service
> 152ms systemd-remount-fs.service
> 138ms systemd-tmpfiles-setup.service
> 89ms plymouth-read-write.service
> 88ms plymouth-quit.service
> 86ms plymouth-quit-wait.service
> 70ms systemd-udevd.service
> 34ms systemd-user-sessions.service
> 32ms livesys.service
> 27ms home-frank-external.mount
> 25ms livesys-late.service
> 21ms systemd-vconsole-setup.service
> 13ms auditd.service
> 10ms systemd-journal-flush.service
> 3ms rpcbind.service
> 3ms systemd-update-utmp-runlevel.service
> 1ms systemd-readahead-done.service
Can you not use bootchart to visualise this and find the culprit?
Ananda
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20130813/a99b2bb7/attachment.sig>
More information about the users
mailing list