Public issue detail

Stuck D-state investigation for systemd-coredump at folio_wait_bit_common

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

highpackage: systemd-coredumpscore: 110reports: 1

Last seen: 2026-05-09 13:01 UTC. Public JSON: /v1/issues/019df3a4-a24d-79a0-9feb-143880a9ef95

Technical snapshot

This is where Fixer saw the sampled task blocked in the kernel.

Kernel wait stack

  • State: R (running)
  • Wait site: 0
  • Kernel: 6.19.14+deb14-amd64
  • Distribution: debian
folio_wait_bit_common
filemap_get_pages
filemap_read
vfs_read
ksys_read
do_syscall_64
entry_SYSCALL_64_after_hwframe

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.

python3.13 shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via folio_wait_bit_common.

highpackage: python3.13-minimalsource: python3.13score: 110reports: 2similarity: 99%

Why this looks related: same classification, same stack or hot path signature, same subsystem, very similar public summary

Last seen: 2026-04-03 22:55 UTC. Public page: /issues/019d3b87-bcdb-7a01-8fd2-53d099979514. Public JSON: /v1/issues/019d3b87-bcdb-7a01-8fd2-53d099979514

ntfs-3g shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via folio_wait_bit_common.

highpackage: ntfs-3gsource: ntfs-3gscore: 110reports: 1similarity: 99%

Why this looks related: same classification, same stack or hot path signature, same subsystem, very similar public summary

Last seen: 2026-05-10 01:29 UTC. Public page: /issues/019e0456-3398-71f3-af80-09a6e84714ef. Public JSON: /v1/issues/019e0456-3398-71f3-af80-09a6e84714ef

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

highpackage: google-chrome-stablesource: google-chrome-stablescore: 110reports: 1similarity: 99%

Why this looks related: same classification, same stack or hot path signature, same subsystem, very similar public summary

Last seen: 2026-05-09 18:43 UTC. Public page: /issues/019d495c-dff5-7b23-b9c4-ca70c7eaed92. Public JSON: /v1/issues/019d495c-dff5-7b23-b9c4-ca70c7eaed92

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

highpackage: rsyncsource: rsyncscore: 110reports: 1similarity: 99%

Why this looks related: same classification, same stack or hot path signature, same subsystem, very similar public summary

Last seen: 2026-05-09 11:15 UTC. Public page: /issues/019e0354-2d9b-7e30-967a-34ffd8a65e18. Public JSON: /v1/issues/019e0354-2d9b-7e30-967a-34ffd8a65e18

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

highpackage: yakuakesource: yakuakescore: 110reports: 1similarity: 99%

Why this looks related: same classification, same stack or hot path signature, same subsystem, very similar public summary

Last seen: 2026-05-07 12:01 UTC. Public page: /issues/019de393-20e4-70e1-9d1f-2b1fbcfe6e89. Public JSON: /v1/issues/019de393-20e4-70e1-9d1f-2b1fbcfe6e89

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

highscore: 110reports: 1similarity: 99%

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

Last seen: 2026-05-02 21:27 UTC. Public page: /issues/019dea04-7baa-7870-90d5-b4d9839ef3ce. Public JSON: /v1/issues/019dea04-7baa-7870-90d5-b4d9839ef3ce

Published attempts

No public attempts have been published for this issue yet.