You are not logged in.
My system boot usually was taking 5-7 seconds, and rebooting/shutdowning was immediate but, recently after I've upgraded the system, boot started to taking almost 10 seconds, and when I run reboot there's a 2 seconds delay. Unfortunately I don't have initramfs-fallback to check if it's the cause of the issue.
I've tried to search something about it but I couldn't find any helpful information.
The most annoying is the 2 seconds delay on shutdown/reboot so I'd be glad if you tell me how I can find out which process creates this delay?
Here's my system configuration.
Linux: linux (6.6.7.arch1-1)
Nvidia driver: nvidia (545.29.06-6)
Filesystem: XFS
Bootloader: efistub
WM: i3wm (without login manager)
Last edited by tayko (2023-12-20 02:16:11)
Offline
systemd-analyze critical-chainAnd please post your complete system journal for the previous boot:
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stOffline
graphical.target @1.948s
└─multi-user.target @1.948s
└─getty.target @1.948s
└─getty@tty1.service @1.948s
└─systemd-user-sessions.service @1.912s +35ms
└─network.target @1.911s
└─systemd-networkd.service @1.791s +120ms
└─systemd-sysctl.service @1.721s +32ms
└─systemd-modules-load.service @471ms +1.209s
└─systemd-journald.socket @460ms
└─-.mount @426ms
└─-.slice @426msOffline
That boot took less than 2 seconds?
This is in line w/ the journal which ends
Oct 16 00:00:48 iusearchbtw systemd-logind[501]: The system will power off at Mon 2023-10-16 00:03:48 +04!
Oct 16 00:01:48 iusearchbtw systemd-logind[501]: The system will power off at Mon 2023-10-16 00:03:48 +04!
Oct 16 00:02:48 iusearchbtw systemd-logind[501]: The system will power off at Mon 2023-10-16 00:03:48 +04!
Oct 16 00:03:48 iusearchbtw systemd-logind[501]: System is powering down.
Oct 16 00:03:48 iusearchbtw systemd-logind[501]: The system will power off now!
…
Oct 16 00:03:50 iusearchbtw systemd-shutdown[1]: Syncing filesystems and block devices.
Oct 16 00:03:50 iusearchbtw systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Oct 16 00:03:50 iusearchbtw systemd-journald[304]: Received SIGTERM from PID 1 (systemd-shutdow).
Oct 16 00:03:50 iusearchbtw systemd-journald[304]: Journal stoppedin a 2s shutdown with the red color around flatpak/portal.
Do you experience the "slow boot and shutdown" also if you only boot the multi-user.target (2nd link below)?
Last edited by seth (2023-12-19 22:12:52)
Offline
Thank you very much for pointing out where to look for the problem. It turned out there was a problem with bluetooth.service, I disabled then enabled it, now the system reboots immediately. Boot time also has been fixed.
I assume it happened when I upgraded bluez together with the system, but I still don't understand how it was affecting the system boot time.
graphical.target @1.822s
└─multi-user.target @1.822s
└─getty.target @1.822s
└─getty@tty1.service @1.822s
└─systemd-user-sessions.service @1.742s +39ms
└─network.target @1.742s
└─systemd-networkd.service @1.695s +46ms
└─systemd-sysctl.service @1.593s +79ms
└─systemd-modules-load.service @361ms +1.200s
└─systemd-journald.socket @349ms
└─system.slice @311ms
└─-.slice @311msYou can see there's only 100ms difference but the total system boot time has been reduced for a 3 seconds. I assume it was something wrong with my usb bluetooth adapter.
That boot took less than 2 seconds?
I was measuring the total system loading time (including the bios).
Offline