Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Michael Biebl]

Am 15.03.2018 um 23:31 schrieb Jeff Ketchum:
> Package: systemd
> Version: 238-2
> Severity: normal
> 
> 
> 
> -- Package-specific info:
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages systemd depends on:
> ii  adduser          3.117
> ii  libacl1          2.2.52-3+b1
> ii  libapparmor1     2.12-3
> ii  libaudit1        1:2.8.2-1
> ii  libblkid1        2.31.1-0.5
> ii  libc6            2.27-2
> ii  libcap2          1:2.25-1.2
> ii  libcryptsetup12  2:2.0.1-1
> ii  libgcrypt20      1.8.1-4
> ii  libgpg-error0    1.27-6
> ii  libidn11         1.33-2.1
> ii  libip4tc0        1.6.2-1
> ii  libkmod2         25-1
> ii  liblz4-1         0.0~r131-2+b1
> ii  liblzma5         5.2.2-1.3
> ii  libmount1        2.31.1-0.5
> ii  libpam0g         1.1.8-3.7
> ii  libseccomp2      2.3.1-2.1
> ii  libselinux1      2.7-2+b1
> ii  libsystemd0      238-2
> ii  mount            2.31.1-0.5
> ii  procps           2:3.3.12-4
> ii  util-linux       2.31.1-0.5
> 
> Versions of packages systemd recommends:
> ii  dbus            1.12.6-2
> ii  libpam-systemd  238-2
> 
> Versions of packages systemd suggests:
> ii  policykit-1        0.105-18
> pn  systemd-container  <none>
> 
> Versions of packages systemd is related to:
> pn  dracut           <none>
> ii  initramfs-tools  0.130
> ii  udev             238-2
> 
> -- Configuration Files:
> /etc/systemd/journald.conf changed:
> [Journal]
> Storage=auto
> 
> 
> -- no debconf information
> 
> I upgraded systemd, and after a failure to boot, realized it was on
> systemd:i386.
> I went into a recovery environment and removed systemd:i386 and
> installed systemd.
> After that It failed to boot at a different location.
> I was able to get it to boot by removing the kernel parameter
> for the nouveau driver to use the binary firmware.
> 
> nouveau.config=NvGrUseFw=1

Where exactly is the problem that is caused by systemd?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180315/81dbc4b2/attachment-0002.sig>