init: Assertion 'hashmap_isempty(m->jobs)' failed at src/core/manager.c:1474, function manager_clear_jobs_and_units(). Aborting. #24577
Description
systemd version the issue has been seen with
251.3
Used distribution
Debian Bullseye
Linux kernel version used
5.15.46
CPU architectures issue was seen on
x86_64
Component
No response
Expected behaviour you didn't see
No crash
Unexpected behaviour you saw
Broadcast message from systemd-journald@133m11 (Tue 2022-09-06 12:18:06 UTC):
systemd[1]: Caught <ABRT> from our own process.
Broadcast message from systemd-journald@133m11 (Tue 2022-09-06 12:18:06 UTC):
systemd[1]: Caught <ABRT>, dumped core as pid 3960.
Broadcast message from systemd-journald@133m11 (Tue 2022-09-06 12:18:06 UTC):
systemd[1]: Freezing execution.
Sep 06 12:18:06 133m11 systemd[1]: Reloading.
Sep 06 12:18:06 133m11 systemd[1]: Assertion 'hashmap_isempty(m->jobs)' failed at src/core/manager.c:1474, function manager_clear_jobs_and_units(). Aborting.
Sep 06 12:18:06 133m11 systemd[1]: Caught <ABRT> from our own process.
Sep 06 12:18:06 133m11 systemd[1]: Caught <ABRT>, dumped core as pid 3960.
Sep 06 12:18:06 133m11 systemd[1]: Freezing execution.
Steps to reproduce the problem
I seemed to manage to trigger this twice during early-boot (over serial console) by calling systemctl stop on two service units and one path unit, right as some initialisation routine calls systemctl daemon-reload.
I'm not sure how to put the system into debug mode from boot. I can tweak the kernel cmdline if necessary, but this happens so early that it's hard to do anything before the window passes.
Additional program output to the terminal or log subsystem illustrating the issue
No response