You are not logged in.
I upgraded to systemd-229-2 and after a reboot, towards the end of the boot process, I get a flashing cursor and no tty login. Here is what I see on screen:
...
[ OK ] Activated swap /dev/sdb3
[ OK ] Reached target Swap.
[ OK ] Reached target System Initialization.
[ OK ] Listening on CUPS Scheduler.
[ OK ] Started Daily Cleanup of Temporary Directories
[ OK ] Started CUPS Scheduler.
[ OK ] Reached target Paths.
_
Downgrading systemd to 228-4 gets me up and running again.
Anybody else having problems with systemd upgrade?
Last edited by jonny_mako (2016-03-08 05:26:01)
Offline
Works fine on all my machines. What is in your journal for the failed boot?
Offline
Works fine on all my machines. What is in your journal for the failed boot?
This looks like the relevant portion of the journal:
Feb 19 00:37:54 <hostname> systemd[1]: Reached target Swap.
Feb 19 00:37:54 <hostname> systemd[1]: Reached target System Initialization.
Feb 19 00:37:54 <hostname> systemd[1]: Listening on CUPS Scheduler.
Feb 19 00:37:54 <hostname> systemd[1]: Assertion '*v' failed at src/core/timer.c:337, function add_random(). Aborting.
I think I'm running into this.
Last edited by jonny_mako (2016-02-19 07:05:05)
Offline
Yes, same here.
Downgrading to 228-4 let the system boots again.
Awaiting the 229-3 get moved to core to try again.
Cheers.
Offline
As expected, update to 229-3 solved the problem here.
Offline
I am still seeing the issue on 229-3 but during shutdown. Had to revert to 228-4
Last edited by bmpro (2016-03-28 03:41:56)
Offline