Public issue detail

Runaway CPU investigation for packagekitd: busy poll at unresolved offset in libglib-2.0.so.0.8800.0

packagekitd is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through 0x000000000005ad75, with repeated ppoll x4, <... ppoll resumed>) = 0 x1, futex x1.

highpackage: packagekitsource: packagekitscore: 106reports: 2

Last seen: 2026-03-29 18:31 UTC. Public JSON: /v1/issues/019d3a09-5db3-70e1-9882-25c4bc1d7196

Technical snapshot

This is the stack-shaped slice and hot path Fixer captured while the process was spinning.

Sampled wait stack

  • Command: /usr/libexec/packagekitd
  • Why Fixer classified it this way: The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.
  • Wait site: poll_schedule_timeout.constprop.0
  • Hot path: 0x000000000005ad75 (100.00% sampled CPU)
  • Repeated loop: futex -> ppoll -> ppoll
  • Top syscalls: ppoll x4, <... ppoll resumed>) = 0 x1, futex x1
  • Package: packagekit
poll_schedule_timeout.constprop.0
do_sys_poll
__x64_sys_ppoll
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.

Runaway CPU investigation for perl: busy poll at unresolved offset in perl

possible duplicate

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f25577e97d2 in ?? () from target:<path>.

highpackage: perl-basesource: perlscore: 106reports: 2successful triagesimilarity: 74%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-05-16 03:22 UTC. Public page: /issues/019dc07f-d19d-7cd0-8771-a7f51e5fec2b. Public JSON: /v1/issues/019dc07f-d19d-7cd0-8771-a7f51e5fec2b

Runaway CPU investigation for rsync: busy poll at unresolved offset in libzstd.so.1.5.7

possible duplicate

rsync is stuck in a likely busy poll loop: 6.00% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f95a089a7d2 in ?? () from target:<path>.

highpackage: rsyncsource: rsyncscore: 106reports: 2patch attempt readysimilarity: 71%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-05-13 06:39 UTC. Public page: /issues/019df882-f473-7f22-92dc-a92df783f924. Public JSON: /v1/issues/019df882-f473-7f22-92dc-a92df783f924

Runaway CPU investigation for python3.13: busy poll at unresolved offset in python3.13

possible duplicate

python3.13 is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () from target:<path>.

highpackage: python3.13-minimalsource: python3.13score: 106reports: 2similarity: 70%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-05-19 01:48 UTC. Public page: /issues/019dc2a0-9ae7-7f42-8f59-415fe22abe51. Public JSON: /v1/issues/019dc2a0-9ae7-7f42-8f59-415fe22abe51

Runaway CPU investigation for perl: busy poll at Perl_runops_standard

possible duplicate

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through Perl_runops_standard, with repeated thread backtraces show 1 thread(s) around 0x00007fce497c17d2 in ?? () from target:<path>.

highpackage: perl-basesource: perlscore: 106reports: 3patch attempt readysimilarity: 60%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-05-19 04:49 UTC. Public page: /issues/019d4017-20f8-7752-9734-0bcd71623118. Public JSON: /v1/issues/019d4017-20f8-7752-9734-0bcd71623118

Runaway CPU investigation for rsync: busy poll at clear_page_erms

possible duplicate

rsync is stuck in a likely busy poll loop: 24.28% of sampled CPU passed through clear_page_erms, with repeated thread backtraces show 1 thread(s) around 0x00007f1f5169a7d2 in ?? () from target:<path>.

highpackage: rsyncsource: rsyncscore: 106reports: 2patch attempt readysimilarity: 59%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-05-19 04:49 UTC. Public page: /issues/019e1a88-12a2-79f0-8a00-0794e663896a. Public JSON: /v1/issues/019e1a88-12a2-79f0-8a00-0794e663896a

Runaway CPU investigation for python3.13: busy poll at read_tsc

possible duplicate

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through read_tsc, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () from target:<path>.

highpackage: python3.13-minimalsource: python3.13score: 106reports: 2similarity: 58%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-05-19 01:01 UTC. Public page: /issues/019da8df-cd0c-7880-ab1e-6dd908d64437. Public JSON: /v1/issues/019da8df-cd0c-7880-ab1e-6dd908d64437

Worker outcome summary

This issue has 3 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.

3 failed patch attempts

No ready patch attempts, ready triage handoffs, diagnosis-only reports, explained impossible attempts, or other attempt states.

Most common blockers

  • patch proposal did not complete cleanly (3 attempts)

Published attempts

failed patch attempt

patch

packagekitd likely remains stuck in a busy poll loop. The diagnosis was captured, but the patch proposal did not complete cleanly.

state: failedcreated: 2026-03-29 15:07 UTCvalidation: failed

Why it stopped

patch proposal did not complete cleanly

Collected context

  • This older failed attempt predates structured patch failure capture, so Fixer only retained the diagnosis and workspace context.
  • Subsystem: runaway-process
  • Diagnosis family: busy-poll
  • Hot path: 0x000000000005ad75
  • Command: /usr/libexec/packagekitd
  • Source package: packagekit
  • Workspace source: debian-source
  • Workspace acquisition: Fetched Debian source package via apt-get source.
  • Homepage: https://www.freedesktop.org/software/PackageKit/
  • Implicated packages: libglib2.0-0t64

The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.

failed patch attempt

patch

packagekitd likely remains stuck in a busy poll loop. The diagnosis was captured, but the patch proposal did not complete cleanly.

state: failedcreated: 2026-03-29 15:06 UTCvalidation: failed

Why it stopped

patch proposal did not complete cleanly

Collected context

  • This older failed attempt predates structured patch failure capture, so Fixer only retained the diagnosis and workspace context.
  • Subsystem: runaway-process
  • Diagnosis family: busy-poll
  • Hot path: 0x000000000005ad75
  • Command: /usr/libexec/packagekitd
  • Source package: packagekit
  • Workspace source: debian-source
  • Workspace acquisition: Fetched Debian source package via apt-get source.
  • Homepage: https://www.freedesktop.org/software/PackageKit/
  • Implicated packages: libglib2.0-0t64

The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.

failed patch attempt

patch

packagekitd likely remains stuck in a busy poll loop. The diagnosis was captured, but the patch proposal did not complete cleanly.

state: failedcreated: 2026-03-29 14:57 UTCvalidation: failed

Why it stopped

patch proposal did not complete cleanly

Collected context

  • This older failed attempt predates structured patch failure capture, so Fixer only retained the diagnosis and workspace context.
  • Subsystem: runaway-process
  • Diagnosis family: busy-poll
  • Hot path: 0x000000000005ad75
  • Command: /usr/libexec/packagekitd
  • Source package: packagekit
  • Workspace source: debian-source
  • Workspace acquisition: Fetched Debian source package via apt-get source.
  • Homepage: https://www.freedesktop.org/software/PackageKit/
  • Implicated packages: libglib2.0-0t64

The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.

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