Arch Linux

LabRicecat

Member

Registered: 2023-09-10

Posts: 39

[SOLVED] systemd-coredump fails due to timeout

Hello, I have been experiencing severe and irregular lag spikes when booting up my PC. CPU nor GPU nor RAM do go up higher than usual, same for disk-usage. After finally looking around, I think I found the culprit.

Checking

journalctl -xe

I discovered that the systemd-coredump timed out after 5 minutes:

Jun 28 07:29:00 meow systemd[1]: systemd-coredump@0-1-2381_8463-0.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-coredump@0-1-2381_8463-0.service has entered the 'failed' state with result 'timeout'.
Jun 28 07:29:00 meow systemd[1]: systemd-coredump@0-1-2381_8463-0.service: Consumed 3.853s CPU time over 5min 6.794s wall clock time, 5.5G memory peak.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-coredump@0-1-2381_8463-0.service completed and consumed the indicated resources.

I could confirm it failing by checking

systemctl --failed

  UNIT                                     LOAD   ACTIVE SUB    DESCRIPTION                       
● systemd-coredump@0-1-2381_8463-0.service loaded failed failed Process Core Dump (PID 2381/UID 0)

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

1 loaded units listed.

This issue persisted even after updating my system fully. I sadly could not find any issues online that seemed related to this, anyone has a clue what might have gone wrong?
I saved the full journalctl -xe and dmesg of this right away.

Thanks a lot!

Last edited by LabRicecat (2026-06-28 08:12:31)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,756

Re: [SOLVED] systemd-coredump fails due to timeout

experiencing severe and irregular lag spikes

Consumed 3.853s CPU time over 5min 6.794s wall clock time, 5.5G memory peak.

If it's related it's gonna be the RAM peak

I assume the reason why it failed  and notably the crash it wanted to process will be very interesting.

systemctl status systemd-coredump@0-1-2381_8463-0.service

see https://wiki.archlinux.org/title/Core_d … _core_dump
In doubt post the entire journal for that boot,:

sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

"-b -1" if you've since then rebooted "1" times.

Please never use -x w/ journalctl, all lines starting w/ ░░ are essentially spam
Fwiw, dmesg is logged in the journal and journald will keep older journals until a disk quota is encountered and then drop the oldest ones.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

LabRicecat

Member

Registered: 2023-09-10

Posts: 39

Re: [SOLVED] systemd-coredump fails due to timeout

If it's related it's gonna be the RAM peak

That'd surprise me, I have 32GB in use, unless I am misreading something, it says to have used "only" 5.5GB.

As for the status of the service, not much I could gather myself either:

× systemd-coredump@0-1-2381_8463-0.service - Process Core Dump (PID 2381/UID 0)
     Loaded: loaded (/usr/lib/systemd/system/systemd-coredump@.service; static)
     Active: failed (Result: timeout) since Sun 2026-06-28 07:29:00 CEST; 1h 26min ago
   Duration: 5min 176ms
 Invocation: 9ea0e63188344023afac0aab27ec0364
TriggeredBy: ● systemd-coredump.socket
       Docs: man:systemd-coredump(8)
    Process: 2395 ExecStart=/usr/lib/systemd/systemd-coredump (code=killed, signal=TERM)
   Main PID: 2395 (code=killed, signal=TERM)
   Mem peak: 5.5G
        CPU: 3.853s

The humble wall of text (aka journal): https://paste.c-net.org/MartinezCleaver

Nothing I could gather so far points me in any direction, however I only scanned quickly over the journal at the time it happened.

EDIT: after looking at the recent coredumps, the latest one present is from last friday, which seems unrelated to this issue.

Last edited by LabRicecat (2026-06-28 07:03:57)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,756

Re: [SOLVED] systemd-coredump fails due to timeout

Jun 28 07:25:56 meow systemd[981]: Dependency failed for Portal service.
Jun 28 07:25:56 meow systemd[981]: xdg-desktop-portal.service: Job xdg-desktop-portal.service/start failed with result 'dependency'.

https://bbs.archlinux.org/viewtopic.php?id=314043
However, the latest xdg-desktop-portal should™ have patched that dependency out.

Jun 28 07:23:53 meow systemd-coredump[2381]: Process 2019 (WebKitWebProces) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Jun 28 07:23:53 meow systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 28 07:23:53 meow systemd[1]: Started Process Core Dump (PID 2381/UID 0).

If that's not in the list of coredumps then because systemd-coredump failed to put it there.

See whether resolving the xdg-d-p situation makes the lags go away (and fixes systemd-coredump)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

LabRicecat

Member

Registered: 2023-09-10

Posts: 39

Re: [SOLVED] systemd-coredump fails due to timeout

Ah, it seems like the system update I did was longer ago than I remembered, I updated accordingly and the service started without issues.
Since the lag has been inconsistent, I will mark this as resolved and reopen in case the same error resurfaces.

Thank you for your time!