Public issue detail

Stuck D-state investigation for yakuake at folio_wait_bit_common

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

highpackage: yakuakesource: yakuakescore: 110reports: 1

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

Technical snapshot

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

Kernel wait stack

  • State: D (disk sleep)
  • Wait site: folio_wait_bit_common
  • Package: yakuake 26.04.0-1
  • Kernel: 6.19.13+deb14-amd64
  • Distribution: debian
folio_wait_bit_common
__folio_lock_or_retry
do_swap_page
__handle_mm_fault
handle_mm_fault
do_user_addr_fault
exc_page_fault
asm_exc_page_fault

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, same wait site, very similar public summary

Last seen: 2026-07-10 04:11 UTC. Public page: /issues/019d3b87-bcdb-7a01-8fd2-53d099979514. Public JSON: /v1/issues/019d3b87-bcdb-7a01-8fd2-53d099979514

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: 2similarity: 99%

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

Last seen: 2026-07-10 04:11 UTC. Public page: /issues/019d495c-dff5-7b23-b9c4-ca70c7eaed92. Public JSON: /v1/issues/019d495c-dff5-7b23-b9c4-ca70c7eaed92

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

highpackage: nodejssource: nodejsscore: 110reports: 1similarity: 99%

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

Last seen: 2026-07-10 04:11 UTC. Public page: /issues/019e80f9-746e-7602-9582-5e0627f34270. Public JSON: /v1/issues/019e80f9-746e-7602-9582-5e0627f34270

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

highscore: 110reports: 1similarity: 99%

Why this looks related: same classification, same stack or hot path signature, same subsystem, same wait site

Last seen: 2026-05-10 06:22 UTC. Public page: /issues/019e0ce7-aaf4-7a13-83b1-08e05d06c5eb. Public JSON: /v1/issues/019e0ce7-aaf4-7a13-83b1-08e05d06c5eb

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, same wait site, 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

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

highpackage: systemd-coredumpscore: 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 13:01 UTC. Public page: /issues/019df3a4-a24d-79a0-9feb-143880a9ef95. Public JSON: /v1/issues/019df3a4-a24d-79a0-9feb-143880a9ef95

Published attempts

No public attempts have been published for this issue yet.