Thanks Jorge. Happy to share ours, with two caveats worth stating first. I cannot symbolise it here. As noted above there are no ESM debug symbols on ddebs and debuginfod does not cover focal, and with +esm4 now withdrawn I cannot fetch the matching binary either.
The second matters more: apport did not catch the faulting thread. ProcStatus shows Pid 570762, PPid 1, so this is the crash handler's fork. Frame 0 is libc-2.31.so +0x433db and frame 1 is systemd +0xbdd63, while the kernel logged the fault itself at +0x7def9, which is not on that stack. The heap should still be PID 1's as at the fault, so watch_pids and unit state ought to be intact, which may be the more useful half here anyway. Particulars: Signal 11, Sat 5 Sep 14:53:34 2026 (UTC+10), 5.15.0-1114-aws, amd64, systemd mapped at 0x55afdf329000 with r-xp text to 0x55afdf3e8000. About 25 MB uncompressed. I have ProcMaps and ProcStatus too. Private would suit better if that offer stands: it is a shared-hosting box, and the unit and cgroup names identify customers. Tell me where to send it and I will include SHA256 checksums. -- 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
