<div dir="ltr">Actually, I was able to just now get it to boot with that config, so this seems to be an intermittent problem. I hit it most of the time.<br>It is during boot, and systemd<br><br>It may not be with systemd, but that is where the upgrades came from, everything else was working before that.<br><br>Here is another failed boot. this is the last thing in the log.<br><br><div>Mar 15 16:54:56 jket-deb NetworkManager[794]: <info> [1521154496.1043] device (enp3s0): carrier: link connected</div><div>Mar 15 16:54:56 jket-deb ModemManager[788]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0': not supported by any plugin</div><div>Mar 15 16:54:56 jket-deb ModemManager[788]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.7/0000:04:00.0': not supported by any plugin</div><div>Mar 15 16:55:26 jket-deb NetworkManager[794]: <info> [1521154526.2209] device (br0): carrier: link connected</div><div>Mar 15 16:55:27 jket-deb avahi-daemon[795]: Joining mDNS multicast group on interface br0.IPv6 with address fe80::fab1:56ff:feb8:524a.</div><div>Mar 15 16:55:27 jket-deb avahi-daemon[795]: New relevant interface br0.IPv6 for mDNS.</div><div>Mar 15 16:55:27 jket-deb avahi-daemon[795]: Registering new address record for fe80::fab1:56ff:feb8:524a on br0.*.</div><div>Mar 15 16:55:29 jket-deb avahi-daemon[795]: Leaving mDNS multicast group on interface br0.IPv6 with address fe80::fab1:56ff:feb8:524a.</div><div>Mar 15 16:55:29 jket-deb avahi-daemon[795]: Joining mDNS multicast group on interface br0.IPv6 with address 2603:3026:414:b1f0:fab1:56ff:feb8:524a.</div><div>Mar 15 16:55:29 jket-deb avahi-daemon[795]: Registering new address record for 2603:3026:414:b1f0:fab1:56ff:feb8:524a on br0.*.</div><div>Mar 15 16:55:29 jket-deb avahi-daemon[795]: Withdrawing address record for fe80::fab1:56ff:feb8:524a on br0.</div><div>Mar 15 16:55:53 jket-deb systemd-udevd[429]: seq 2260 '/devices/pci0000:00/0000:00:01.0/0000:01:00.0' is taking a long time</div><div>Mar 15 16:55:55 jket-deb systemd-udevd[429]: seq 3061 '/devices/virtual/vtconsole/vtcon1' is taking a long time</div><div>Mar 15 16:57:53 jket-deb systemd-udevd[429]: seq 2260 '/devices/pci0000:00/0000:00:01.0/0000:01:00.0' killed</div><div>Mar 15 16:57:55 jket-deb systemd-udevd[429]: seq 3061 '/devices/virtual/vtconsole/vtcon1' killed</div><div>Mar 15 16:57:55 jket-deb systemd-udevd[429]: worker [466] terminated by signal 9 (KILL)</div><div>Mar 15 16:57:55 jket-deb systemd-udevd[429]: worker [466] failed while handling '/devices/virtual/vtconsole/vtcon1'</div><div>Mar 15 17:00:38 jket-deb NetworkManager[794]: <info> [1521154838.7769] device (wlp4s0): set-hw-addr: set MAC address to 6E:1A:B4:B7:1B:66 (scanning)</div><div>Mar 15 17:00:38 jket-deb NetworkManager[794]: <info> [1521154838.7973] device (wlp4s0): supplicant interface state: ready -> disabled</div><div>Mar 15 17:00:38 jket-deb NetworkManager[794]: <info> [1521154838.8324] device (wlp4s0): supplicant interface state: disabled -> inactive</div><div>Mar 15 17:00:38 jket-deb wpa_supplicant[793]: wlp4s0: Reject scan trigger since one is already pending</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 15, 2018 at 4:40 PM, Michael Biebl <span dir="ltr"><<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Am 15.03.2018 um 23:31 schrieb Jeff Ketchum:<br>
> Package: systemd<br>
> Version: 238-2<br>
> Severity: normal<br>
><br>
><br>
><br>
> -- Package-specific info:<br>
><br>
> -- System Information:<br>
> Debian Release: buster/sid<br>
> APT prefers unstable<br>
> APT policy: (500, 'unstable')<br>
> Architecture: amd64 (x86_64)<br>
> Foreign Architectures: i386<br>
><br>
> Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU cores)<br>
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)<br>
> Shell: /bin/sh linked to /bin/dash<br>
> Init: systemd (via /run/systemd/system)<br>
> LSM: AppArmor: enabled<br>
><br>
> Versions of packages systemd depends on:<br>
> ii adduser 3.117<br>
> ii libacl1 2.2.52-3+b1<br>
> ii libapparmor1 2.12-3<br>
> ii libaudit1 1:2.8.2-1<br>
> ii libblkid1 2.31.1-0.5<br>
> ii libc6 2.27-2<br>
> ii libcap2 1:2.25-1.2<br>
> ii libcryptsetup12 2:2.0.1-1<br>
> ii libgcrypt20 1.8.1-4<br>
> ii libgpg-error0 1.27-6<br>
> ii libidn11 1.33-2.1<br>
> ii libip4tc0 1.6.2-1<br>
> ii libkmod2 25-1<br>
> ii liblz4-1 0.0~r131-2+b1<br>
> ii liblzma5 5.2.2-1.3<br>
> ii libmount1 2.31.1-0.5<br>
> ii libpam0g 1.1.8-3.7<br>
> ii libseccomp2 2.3.1-2.1<br>
> ii libselinux1 2.7-2+b1<br>
> ii libsystemd0 238-2<br>
> ii mount 2.31.1-0.5<br>
> ii procps 2:3.3.12-4<br>
> ii util-linux 2.31.1-0.5<br>
><br>
> Versions of packages systemd recommends:<br>
> ii dbus 1.12.6-2<br>
> ii libpam-systemd 238-2<br>
><br>
> Versions of packages systemd suggests:<br>
> ii policykit-1 0.105-18<br>
> pn systemd-container <none><br>
><br>
> Versions of packages systemd is related to:<br>
> pn dracut <none><br>
> ii initramfs-tools 0.130<br>
> ii udev 238-2<br>
><br>
> -- Configuration Files:<br>
> /etc/systemd/journald.conf changed:<br>
> [Journal]<br>
> Storage=auto<br>
><br>
><br>
> -- no debconf information<br>
><br>
> I upgraded systemd, and after a failure to boot, realized it was on<br>
> systemd:i386.<br>
> I went into a recovery environment and removed systemd:i386 and<br>
> installed systemd.<br>
> After that It failed to boot at a different location.<br>
> I was able to get it to boot by removing the kernel parameter<br>
> for the nouveau driver to use the binary firmware.<br>
><br>
> nouveau.config=NvGrUseFw=1<br>
<br>
Where exactly is the problem that is caused by systemd?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Why is it that all of the instruments seeking intelligent life in the<br>
universe are pointed away from Earth?<br>
<br>
</font></span></blockquote></div><br></div>