You are not logged in.
Latest systemd update (246-1) is just broken. It's even can't install properly. Post-transaction hooks failed, it was not able to restart some services, the system started to lag and randomly not responding. But well ok, **it happens, reboot.
And here is the main trouble: after boot tty can't start around a minute! Login prompt just doesn't appear. Seems like the tty service is not responding during this time. After it timed out and restarted, this message appears in the journal:
systemd-logind[537]: Failed to start autovt@tty2.service: No buffer space available
Just it and nothing else. I have only one question: watta hell?
P. S. Display manager service (lightdm) autostarts instantly and loads DE without troubles.
Last edited by Hanabishi (2020-08-07 16:30:16)
Offline
Also just noticed such messages on boot:
systemd[1]: initrd-switch-root.service: Current command vanished from the unit file, execution of the command list won't be resumed.
systemd[1]: initrd-switch-root.service: Succeeded.
And systemd drains 100% CPU constantly:
And systemctl is basically dead:
Last edited by Hanabishi (2020-08-07 08:56:37)
Offline
Also just noticed such messages on boot:
systemd[1]: initrd-switch-root.service: Current command vanished from the unit file, execution of the command list won't be resumed. systemd[1]: initrd-switch-root.service: Succeeded.
Offline
Yeah, already found it too. Unfortunately doesn't help.
Btw 245 systemd version, that this report for, doesn't had this issue for me.
Offline
Did you regenerate initramfs (mkinitcpio -P) after changes?
If you have systemd in HOOKS() in mkinitcpio.conf, try use udev instead.
Offline
Did you regenerate initramfs (mkinitcpio -P) after changes?
Of course. Also reinstalled systemd package several times that automatically triggers mkinitcpio.
If you have systemd in HOOKS() in mkinitcpio.conf, try use udev instead.
Wow, seems like this actually helped! My hooks line was
HOOKS=(base systemd block keyboard fsck filesystems)
Changing systemd to udev required some bootloader reconfiguration (explicitly set a root partition in kernel options, systemd was able to find it automatically).
This is mostly workaround than a fix, but the system works properly now, thanks!
Offline
Marking thread as solved.
Go to related issue https://github.com/systemd/systemd/issues/16076
Offline