Public issue detail

Runaway CPU investigation for packagekitd: dbus spin at sched_balance_newidle

packagekitd is stuck in a likely dbus spin loop: 100.00% of sampled CPU passed through sched_balance_newidle, with repeated ppoll x16, write x15, read x9.

highpackage: packagekitsource: packagekitscore: 106reports: 1

Last seen: 2026-03-29 16:21 UTC. Public JSON: /v1/issues/019d3a0c-05f6-7a72-8eda-ec8a424ffe94

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 is dominated by DBus-style socket activity and DBus-related symbols, which looks like a message-loop spin.
  • Wait site: poll_schedule_timeout.constprop.0
  • Hot path: sched_balance_newidle (100.00% sampled CPU)
  • Repeated loop: <... -> write -> ppoll
  • Top syscalls: ppoll x16, write x15, read x9, poll x6
  • Package: packagekit
poll_schedule_timeout.constprop.0
do_poll.constprop.0
do_sys_poll
__x64_sys_ppoll
x64_sys_call
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 packagekitd: busy poll at syscall_return_via_sysret

possible duplicate

packagekitd is stuck in a likely busy poll loop: 24.42% of sampled CPU passed through syscall_return_via_sysret, with repeated ppoll x4, futex x1.

highpackage: packagekitsource: packagekitscore: 106reports: 2successful triagesimilarity: 83%

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

Last seen: 2026-06-10 00:40 UTC. Public page: /issues/019d3a77-60b8-79b3-885c-baaa0251e70f. Public JSON: /v1/issues/019d3a77-60b8-79b3-885c-baaa0251e70f

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 pselect6 x4.

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

Why this looks related: same subsystem, same wait site

Last seen: 2026-06-10 00:40 UTC. Public page: /issues/019d4017-20f8-7752-9734-0bcd71623118. Public JSON: /v1/issues/019d4017-20f8-7752-9734-0bcd71623118

Runaway CPU investigation for perl: busy poll at rb_erase

possible duplicate

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

highpackage: perl-basesource: perlscore: 106reports: 1similarity: 46%

Why this looks related: same subsystem, same wait site

Last seen: 2026-06-04 21:19 UTC. Public page: /issues/019e8f7a-7c69-7b52-9e9e-6890b1ecf321. Public JSON: /v1/issues/019e8f7a-7c69-7b52-9e9e-6890b1ecf321

Runaway CPU investigation for perl: busy poll at Perl_mg_find

possible duplicate

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

highpackage: perl-basesource: perlscore: 106reports: 1similarity: 45%

Why this looks related: same subsystem, same wait site

Last seen: 2026-06-03 21:35 UTC. Public page: /issues/019e7092-7bda-7273-8ce3-7e732bc3782d. Public JSON: /v1/issues/019e7092-7bda-7273-8ce3-7e732bc3782d

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.

4 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 (4 attempts)

Published attempts

failed patch attempt

patch

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

state: failedcreated: 2026-03-29 15:12 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: dbus-spin
  • Hot path: sched_balance_newidle
  • 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: linux-image-6.17.0-14-generic

The trace is dominated by DBus-style socket activity and DBus-related symbols, which looks like a message-loop spin.

failed patch attempt

patch

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

state: failedcreated: 2026-03-29 14:52 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: dbus-spin
  • Hot path: sched_balance_newidle
  • 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: linux-image-6.17.0-14-generic

The trace is dominated by DBus-style socket activity and DBus-related symbols, which looks like a message-loop spin.

failed patch attempt

patch

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

state: failedcreated: 2026-03-29 14:50 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: dbus-spin
  • Hot path: sched_balance_newidle
  • 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: linux-image-6.17.0-14-generic

The trace is dominated by DBus-style socket activity and DBus-related symbols, which looks like a message-loop spin.

failed patch attempt

patch

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

state: failedcreated: 2026-03-29 14:43 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: dbus-spin
  • Hot path: sched_balance_newidle
  • 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: linux-image-6.17.0-14-generic

The trace is dominated by DBus-style socket activity and DBus-related symbols, which looks like a message-loop spin.

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