Your message dated Fri, 20 Nov 2015 14:29:11 +0100
with message-id <[email protected]>
and subject line Re: Bug#800528: systemd: Systemd cannot boot. sysvinit works.
has caused the Debian Bug report #800528,
regarding systemd: Systemd cannot boot. sysvinit works.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
800528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800528
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Am 30.09.2015 um 15:19 schrieb Michael Biebl:
> Btw, you already reported
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794264
> where we've been asking for the same information and didn't receive any
> so far.
>
> Is this bug report different in any way or why did you file a new one?
No feedback so far for both bug reports and with the existing
information it's not possible to further investigate this issue. Thus
closing both
If you still encounter issues with recent versions of systemd, please
file a new bug report and if necessary, provide the requested information.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
