Package: systemd Version: 226-3 Severity: important On two of my machines, I have been unable to boot with systemd for some time. Using the sysvinit fallback (init=/lib/sysvinit/init) does allow full boot.
On this machine systemd simply stops (I do not know if this is deadlock or livelock) but the machine is unresponsive. The screen display is a few 10s of lines after the nouveau driver is loaded and the display is refreshed as a result. I do not suspect the nouveau driver which works with a sysvinit boot. Even under sysvinit, upgrading also hits problems with the rsyslog service, but I don't know whether this is related. Sorry that I have so little useful information. -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: unable to detect Versions of packages systemd depends on: ii adduser 3.113+nmu3 ii libacl1 2.2.52-2 ii libapparmor1 2.9.2-3 ii libaudit1 1:2.4.4-3+b1 ii libblkid1 2.27-3 ii libc6 2.19-22 ii libcap2 1:2.24-11 ii libcap2-bin 1:2.24-11 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod2 21-1 ii liblzma5 5.1.1alpha+20120614-2.1 ii libmount1 2.27-3 ii libpam0g 1.1.8-3.1 ii libseccomp2 2.2.3-2 ii libselinux1 2.3-2+b1 ii libsystemd0 226-3 ii mount 2.27-3 ii sysv-rc 2.88dsf-59.2 ii udev 226-3 ii util-linux 2.27-3 Versions of packages systemd recommends: ii dbus 1.10.0-3 ii libpam-systemd 226-3 Versions of packages systemd suggests: pn systemd-container <none> pn systemd-ui <none> -- no debconf information
