Your message dated Wed, 17 Jun 2015 08:16:58 +0200
with message-id <[email protected]>
and subject line Re: Bug#788913: systemd prevents to boot with a kernel panic.
Boot in systemv mode is ok
has caused the Debian Bug report #788913,
regarding boot failure with separate /usr and no initramfs due to libseccomp
being in /usr
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.)
--
788913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788913
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 220-6
Severity: critical
Justification: breaks the whole system
After yesterday upgrade to systemd 220.6, my system no longer boot. It reports
a kernel panic witha attempting to kill init. I guess a kind of fault occurs in
the daemon but I cannot easilly find traces.
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.4 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF8)
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.2-1
ii libblkid1 2.26.2-7
ii libc6 2.21-0experimental0
ii libcap2 1:2.24-9
ii libcap2-bin 1:2.24-9
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.3-2
ii libkmod2 20-1
ii liblzma5 5.1.1alpha+20120614-2+b3
ii libmount1 2.26.2-7
ii libpam0g 1.1.8-3.1
ii libseccomp2 2.2.1-1
ii libselinux1 2.4-1
ii libsystemd0 220-6
ii mount 2.26.2-7
ii sysv-rc 2.88dsf-59.2
ii udev 220-6
ii util-linux 2.26.2-7
Versions of packages systemd recommends:
ii dbus 1.9.16-2
ii libpam-systemd 220-6
Versions of packages systemd suggests:
pn systemd-ui <none>
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
Martin Pitt [2015-06-16 14:40 +0200]:
> [email protected] [2015-06-16 13:18 +0200]:
> > This has been fixed for apparmor, why not for seccomp?
>
> I filed a bug about it and pinged the maintainer; I don't see a reason
> why it shouldn't get fixed.
This was fixed in libseccomp 2.2.1-2, so after a dist-upgrade your
system should boot fine again. I'm closing this report as there's
nothing much else that we can do in the systemd source package at this
point.
> > Can't you add a test at build time that checks that systemd does not depend
> > on /usr/lib libraries? (ldd systemd | grep /usr/lib => automatically detect
> > possible breakage before they really happen).
>
> Yes, that sounds like a good idea. I'll do that after libseccomp gets
> fixed.
Done so now:
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=24b267b
Thanks,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
