-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Labels
regression ⚠️A bug in something that used to work correctly and broke through some recent commitA bug in something that used to work correctly and broke through some recent commit
Milestone
Description
systemd version the issue has been seen with
244.2
Used distribution
ArchLinux - Linux scout 5.5.2-arch1-1 SMP PREEMPT Tue, 04 Feb 2020 18:56:18 +0000 x86_64 GNU/Linux
Expected behaviour you didn't see
3 seconds user space boot time
Unexpected behaviour you saw
40 seconds user space boot time
Steps to reproduce the problem
sudo pacman -U /var/cache/pacman/pkg/systemd-244.2-1-x86_64.pkg.tar.zst && reboot
Boot times & critical chain on 244.1
[andre@scout ~]$ systemd-analyze
Startup finished in 5.454s (kernel) + 2.843s (userspace) = 8.297s
graphical.target reached after 2.843s in userspace
andre@scout ~]$ 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 @2.843s
└─multi-user.target @2.842s
└─systemd-logind.service @1.692s +1.149s
└─basic.target @1.685s
└─sockets.target @1.685s
└─org.cups.cupsd.socket @1.685s
└─sysinit.target @1.679s
└─systemd-timesyncd.service @1.461s +218ms
└─systemd-tmpfiles-setup.service @1.433s +24ms
└─local-fs.target @1.432s
└─mnt-data.mount @1.393s +39ms
└─systemd-fsck@dev-disk-by\x2duuid-693c2dae\x2d3f8d\x2d4825\x2dbfdf\x2d9268a8b9584b.service @1.305s +86ms
└─local-fs-pre.target @1.304s
└─lvm2-monitor.service @211ms +1.092s
└─lvm2-lvmetad.service @227ms
└─systemd-journald.socket @208ms
└─-.mount @198ms
└─system.slice @198ms
└─-.slice @198ms
Boot times & critical chain on 244.2
[andre@scout ~]$ systemd-analyze
Startup finished in 9.144s (kernel) + 40.945s (userspace) = 50.089s
graphical.target reached after 40.944s in userspace
[andre@scout ~]$ 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 @40.944s
└─multi-user.target @40.943s
└─systemd-logind.service @38.863s +2.077s
└─basic.target @38.855s
└─sockets.target @38.855s
└─org.cups.cupsd.socket @38.854s
└─sysinit.target @38.848s
└─systemd-update-done.service @38.257s +590ms
└─systemd-journal-catalog-update.service @35.780s +2.475s
└─systemd-tmpfiles-setup.service @33.729s +2.050s
└─local-fs.target @33.728s
└─mnt-gamessd.mount @33.720s +8ms
└─systemd-fsck@dev-disk-by\x2duuid-f9ac8e20\x2d5991\x2d4af3\x2d8763\x2d0c7a693bb7db.service @30.269s +3.449s
└─local-fs-pre.target @30.262s
└─lvm2-monitor.service @7.747s +22.514s
└─lvm2-lvmetad.service @7.758s
└─systemd-journald.socket @7.743s
└─system.slice @7.732s
└─-.slice @7.732s
Metadata
Metadata
Assignees
Labels
regression ⚠️A bug in something that used to work correctly and broke through some recent commitA bug in something that used to work correctly and broke through some recent commit