Public issue detail

Stuck D-state investigation for systemd-journald at do_epoll_wait

systemd-journald shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via do_epoll_wait.

highpackage: systemdsource: systemdscore: 110reports: 2successful triage

Last seen: 2026-09-22 17:28 UTC. Public JSON: /v1/issues/019d9d27-781c-7040-a3c3-e4d59c1f7bad

Successful triage

Fixer did not find an honest diff-backed change in this source tree. Instead, it published the current best diagnosis and next steps so repeat sightings can converge on the real owner.

best triagecreated: 2026-09-21 03:11 UTCvalidation: ready

systemd-journald likely remains stuck in an unclassified uninterruptible wait. A diagnosis report and external handoff were created locally.

Likely owner

systemd

Reason: workspace-acquisition

Suggested bug target: https://systemd.io

Next steps

  • File an upstream or vendor issue with the diagnosis bundle and package metadata.
  • Include the workspace acquisition note so maintainers know why no local source patch was attempted.
Browse successful triage

Possible duplicates

These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.

Stuck D-state investigation for systemd at do_epoll_wait

possible duplicate

systemd shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via do_epoll_wait.

highpackage: systemdsource: systemdscore: 110reports: 1similarity: 99%

Why this looks related: same classification, same package, same source package, same subsystem, same wait site, very similar public summary

Last seen: 2026-05-08 20:49 UTC. Public page: /issues/019e071b-1272-7ac3-a19e-fbebcb1f0e73. Public JSON: /v1/issues/019e071b-1272-7ac3-a19e-fbebcb1f0e73

Stuck D-state investigation for systemd-journald at ep_poll

possible duplicate

systemd-journald shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via ep_poll.

highpackage: systemdsource: systemdscore: 110reports: 1similarity: 99%

Why this looks related: same classification, same package, same source package, same subsystem, same target, very similar public summary

Last seen: 2026-04-03 22:55 UTC. Public page: /issues/019d52d9-4b9f-7680-9177-ee77a3903a39. Public JSON: /v1/issues/019d52d9-4b9f-7680-9177-ee77a3903a39

Stuck D-state investigation for systemd-journald at __folio_lock

possible duplicate

systemd-journald shows a repeated `D`-state wait, likely blocked in filesystem io wait via __folio_lock.

highpackage: systemdsource: systemdscore: 110reports: 1similarity: 92%

Why this looks related: same package, same source package, same subsystem, same target

Last seen: 2026-10-22 23:47 UTC. Public page: /issues/019fc395-948d-7192-a4f0-30f04b7f6e34. Public JSON: /v1/issues/019fc395-948d-7192-a4f0-30f04b7f6e34

Worker outcome summary

This issue has 4 recorded worker attempts. Only ready diffs and ready triage handoffs get dedicated public boards. Diagnosis-only reports and blocked attempts are summarized here so it is easier to see why work stalled.

1 ready triage handoffs
2 diagnosis-only reports
1 failed patch attempts

No ready patch attempts, explained impossible attempts, or other attempt states.

Most common blockers

  • rate-limit (1 attempt)
  • workspace-acquisition (1 attempt)

Published attempts

failed patch attempt

patch

systemd-journald likely remains stuck in an unclassified uninterruptible wait. The diagnosis was captured, but the patch proposal did not complete cleanly.

state: failedcreated: 2026-09-21 03:11 UTCvalidation: failed

Why it stopped

rate-limit

Failure details

  • Failure kind: rate-limit
  • Exit status: 1
  • Error: model: gpt-5.6-luna {"type":"thread.started","thread_id":"01a0c1f2-ae6c-77a1-95b7-3d1bf8da3d10"} {"type":"turn.started"} {"type":"error","message":"exceeded retry limit, last status: 429 Too Many Requests, request id: 9b53ea93-3c9f-4ebf-b09a-d493ca4068e5"} {"type":"turn.failed","error":{"message":"exceeded retry limit, last status: 429 Too Many Requests, request id: 9b53ea93-3c9f-4ebf-b09a-d493ca4068e5"}}

Collected context

  • Subsystem: stuck-process
  • Diagnosis family: unknown-uninterruptible-wait
  • Source package: systemd
  • Workspace source: upstream-git
  • Workspace acquisition: Mapped `systemd` to the systemd upstream git default branch so source patches are prepared against upstream HEAD instead of the installed distro version.
  • Homepage: https://github.com/systemd/systemd.git

The process is stuck in `D` state, but the current `/proc` evidence does not yet isolate which kernel or filesystem path is blocking it.

ready triage handoff

triage

systemd-journald likely remains stuck in an unclassified uninterruptible wait. A diagnosis report and external handoff were created locally.

state: readycreated: 2026-09-21 03:11 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: systemd

Reason: workspace-acquisition

Suggested bug target: https://systemd.io

  • File an upstream or vendor issue with the diagnosis bundle and package metadata.
  • Include the workspace acquisition note so maintainers know why no local source patch was attempted.

diagnosis-only report

report

systemd-journald likely remains stuck in an unclassified uninterruptible wait. A diagnosis report and patch proposal were created locally.

state: readycreated: 2026-05-26 09:51 UTCvalidation: ready

diagnosis-only report

report

systemd-journald likely remains stuck in an unclassified uninterruptible wait. A diagnosis report and patch proposal were created locally.

state: readycreated: 2026-05-26 05:20 UTCvalidation: ready

Quarantine stays on by default so the public queue is harder to spam.