Public issue detail

Stuck D-state investigation for qemu-arm at jbd2_log_wait_commit

qemu-arm shows a repeated `D`-state wait, likely blocked in filesystem io wait via jbd2_log_wait_commit.

highpackage: qemu-usersource: qemuscore: 110reports: 1

Last seen: 2026-10-22 23:47 UTC. Public JSON: /v1/issues/019f9fdf-462b-70b3-b83a-cdda32239a87

Technical snapshot

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

Kernel wait stack

  • State: D (disk sleep)
  • Wait site: jbd2_log_wait_commit
  • Package: qemu-user 1:11.0.3+ds-2
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
jbd2_log_wait_commit
__jbd2_journal_force_commit
jbd2_journal_force_commit
ext4_sync_file
do_fsync
__x64_sys_fsync
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.

qemu-s390x shows a repeated `D`-state wait, likely blocked in filesystem io wait via jbd2_log_wait_commit.

highpackage: qemu-usersource: qemuscore: 110reports: 1similarity: 99%

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

Last seen: 2026-10-22 23:47 UTC. Public page: /issues/019f9e97-d29d-79f3-8bb5-f1d70154ade6. Public JSON: /v1/issues/019f9e97-d29d-79f3-8bb5-f1d70154ade6

qemu-arm shows a repeated `D`-state wait, likely blocked in overlayfs wait via jbd2_log_wait_commit.

highpackage: qemu-usersource: qemuscore: 110reports: 1similarity: 99%

Why this looks related: same package, same public title, same source package, same stack or hot path signature, same subsystem, same target, same wait site

Last seen: 2026-10-22 23:47 UTC. Public page: /issues/019fa390-5341-7460-8d5a-ac9c68fa8547. Public JSON: /v1/issues/019fa390-5341-7460-8d5a-ac9c68fa8547

git shows a repeated `D`-state wait, likely blocked in filesystem io wait via jbd2_log_wait_commit.

highpackage: gitsource: gitscore: 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-08-15 06:33 UTC. Public page: /issues/019f7e4d-f862-7c90-913f-f2ae2b219b96. Public JSON: /v1/issues/019f7e4d-f862-7c90-913f-f2ae2b219b96

dpkg shows a repeated `D`-state wait, likely blocked in filesystem io wait via jbd2_log_wait_commit.

highpackage: dpkgsource: dpkgscore: 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-08-15 06:33 UTC. Public page: /issues/019f9d80-1964-77c1-8d4b-573f7dcf48c1. Public JSON: /v1/issues/019f9d80-1964-77c1-8d4b-573f7dcf48c1

NetworkManager shows a repeated `D`-state wait, likely blocked in filesystem io wait via jbd2_log_wait_commit.

highpackage: network-managersource: network-managerscore: 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-08-09 16:55 UTC. Public page: /issues/019fa955-0397-7eb0-863b-6b9e4418e68b. Public JSON: /v1/issues/019fa955-0397-7eb0-863b-6b9e4418e68b

qemu-aarch64 shows a repeated `D`-state wait, likely blocked in filesystem io wait via jbd2_log_wait_commit.

highpackage: qemu-usersource: qemuscore: 110reports: 1similarity: 99%

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

Last seen: 2026-08-01 23:35 UTC. Public page: /issues/019f9d5f-60a3-78d1-9674-502c8c3ca2b0. Public JSON: /v1/issues/019f9d5f-60a3-78d1-9674-502c8c3ca2b0

Published attempts

No public attempts have been published for this issue yet.