We've experienced the same bug in the span of around 5 days on 5 of our 12 server-vm's on Ubuntu 20.04, on ppc64le (IBM Power 8), so very different hardware and setups than both David and Steve.
Unfortunately i only kept the first crash i found: segfault (11) at 65 nip 7186877916d8 lr 7186877916c8 code 1 in libsystemd-shared-245.so [718687620000+320000] code: f8010090 893f002f 71290004 41820008 389f0010 3ba10028 7fa3eb78 4bfce1e5 code: 60000000 e93f0000 7fa4eb78 7f83e378 <e9890000> 7d8903a6 4e800421 e8410018 If any useful information will survive a reboot, i'll happily provide it. We've successfully rolled back all 12 machines using this command: apt install --allow-downgrades \ systemd=245.4-4ubuntu3.24+esm3 \ libsystemd0=245.4-4ubuntu3.24+esm3 \ systemd-sysv=245.4-4ubuntu3.24+esm3 \ systemd-timesyncd=245.4-4ubuntu3.24+esm3 \ libpam-systemd=245.4-4ubuntu3.24+esm3 \ libnss-systemd=245.4-4ubuntu3.24+esm3 And then reboot -f on the machine where systemd already was crashed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2166539 Title: systemd 245.4-4ubuntu3.24+esm4 crashes repeatedly and with increasing frequency after upgrade from +esm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2166539/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
