systemd-journald coredumps after resuming from s2idle
[ 570.823229] systemd-coredump[1732]: Process 299 (systemd-journal) of user 0 dumped core.
[ 570.840744] systemd-coredump[1732]: Coredump diverted to /var/lib/systemd/coredump/core.systemd-journal.0.010f858170514833943a1cb3f976d6cc.299.1637926495000000.zst
[ 570.858423] systemd-coredump[1732]: Stack trace of thread 299:
[ 570.864666] systemd-coredump[1732]: #0 0x0000aaaad3356b10 n/a (systemd-journald + 0x6b10)
[ 570.875873] systemd-coredump[1732]: #1 0x0000aaaad33600c4 n/a (systemd-journald + 0x100c4)
[ 570.884546] systemd-coredump[1732]: #2 0x0000ffff8486de88 n/a (libsystemd-shared-247.so + 0x1bbe88)
[ 570.893849] systemd-coredump[1732]: #3 0x0000000000000011 n/a (n/a + 0x0)
[ 570.928113] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT
[ 570.928437] systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
[ 570.929684] systemd[1]: systemd-journald.service: Consumed 1.408s CPU time.
[ 570.934035] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
[ 570.945383] systemd[1]: Stopping Flush Journal to Persistent Storage...
[ 570.966507] systemd[1]: systemd-journal-flush.service: Succeeded.
[ 570.967474] systemd[1]: Stopped Flush Journal to Persistent Storage.
[ 570.968915] systemd[1]: Stopped Journal Service.
[ 570.969114] systemd[1]: systemd-journald.service: Consumed 1.408s CPU time.
[ 570.976633] systemd[1]: Starting Journal Service...
[ 571.103759] systemd[1]: Started Journal Service.
[ 571.133979] systemd-journald[1762]: Received client request to flush runtime journal.
this could be
https://github.com/systemd/systemd/issues/9538 and the discussion linked there: https://bugzilla.kernel.org/show_bug.cgi?id=200595
so this should go away when switching to suspend to ram / deep sleep.