This can be recreated by stopping the ipmi service with command systemctl stop phosphor-ipmi-host or killall. It appears the ipmi app is not handling signals gracefully:
journalctl
root@fp5280g2:/lib/systemd/system# systemctl stop phosphor-ipmi-host.service
Apr 03 21:00:42 fp5280g2 ipmid[343]: Command in process, no attention
Apr 03 21:00:42 fp5280g2 ipmid[343]: Command in process, no attention
Apr 03 21:00:42 fp5280g2 systemd[1]: Stopping Phosphor MBOX Daemon...
Apr 03 21:00:42 fp5280g2 systemd[1]: mboxd.service: Deactivated successfully.
Apr 03 21:00:42 fp5280g2 systemd[1]: Stopped Phosphor MBOX Daemon.
Apr 03 21:00:42 fp5280g2 ipmid[343]: Received signal; quitting
Apr 03 21:00:42 fp5280g2 systemd[1]: Stopping Phosphor Inband IPMI...
Apr 03 21:00:43 fp5280g2 systemd[1]: Created slice Slice /system/systemd-coredump.
Apr 03 21:00:43 fp5280g2 systemd[1]: Started Process Core Dump (PID 396/UID 0).
root@fp5280g2:/lib/systemd/system# Apr 03 21:00:44 fp5280g2 systemd-coredump[397]: elfutils disabled, parsing ELF objects not supported
Apr 03 21:00:44 fp5280g2 systemd-coredump[397]: [LNK] Process 343 (ipmid) of user 0 dumped core.
Apr 03 21:00:44 fp5280g2 systemd[1]: phosphor-ipmi-host.service: Main process exited, code=dumped, status=11/SEGV
Apr 03 21:00:44 fp5280g2 systemd[1]: phosphor-ipmi-host.service: Failed with result 'core-dump'.
Apr 03 21:00:44 fp5280g2 systemd[1]: Stopped Phosphor Inband IPMI.
Apr 03 21:00:44 fp5280g2 systemd[1]: systemd-coredump@0-396-0.service: Deactivated successfully.
This can be recreated by stopping the ipmi service with command
systemctl stop phosphor-ipmi-host
orkillall
. It appears the ipmi app is not handling signals gracefully:journalctl
core dump file: core.ipmid.tar.gz
Parsed coreDump file