Public issue detail

Runaway CPU investigation for perl: busy poll at unresolved offset in libc.so.6

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 0x00007f2612d297d2 in ?? () from target:<path>.

highpackage: perl-basesource: perlscore: 106reports: 1

Last seen: 2026-06-10 02:24 UTC. Public JSON: /v1/issues/019dc199-535d-7c90-9b68-f6459f9c134d

Technical snapshot

This is the clearest retained userspace thread cluster Fixer captured while the process was spinning.

Representative thread backtrace

  • Command: /usr/bin/perl -wT /usr/sbin/munin-node --foreground
  • 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.
  • Thread summary: thread backtraces show 1 thread(s) around 0x00007f2612d297d2 in ?? () from target:<path>
  • Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory.
  • Repeated loop: pselect6 -> pselect6 -> pselect6
  • Top syscalls: pselect6 x4
  • Package: perl-base 5.40.1-7+b1
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007f2612d297d2 in ?? () from target:<path>
0x00007f2612d297ed in ?? () from target:<path>
0x00007f2612da96cf in select () from target:<path>
0x000055e02267fee4 in ?? ()
0x000055e0226e1496 in Perl_runops_standard ()
0x000055e0225c7b85 in perl_run ()
0x000055e02259a5ae in main ()

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 postgres: busy poll at unresolved offset in libc.so.6

possible duplicate

postgres 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 0x00007f322d29a7d2 in ?? () from target:<path>.

highpackage: postgresql-18source: postgresql-18score: 106reports: 2successful triagesimilarity: 99%

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

Last seen: 2026-06-08 02:57 UTC. Public page: /issues/019dd153-80e7-7d40-b63c-d601fdb0ed31. Public JSON: /v1/issues/019dd153-80e7-7d40-b63c-d601fdb0ed31

Runaway CPU investigation for perl: busy poll at __hrtimer_setup

possible duplicate

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

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

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

Last seen: 2026-06-05 21:37 UTC. Public page: /issues/019e9492-ba96-7f00-9599-ad575e4de4ca. Public JSON: /v1/issues/019e9492-ba96-7f00-9599-ad575e4de4ca

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

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

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

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

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

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: 98%

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

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

Runaway CPU investigation for redis-check-rdb: busy poll at unresolved offset in libc.so.6

possible duplicate

redis-check-rdb is stuck in a likely busy poll loop: 6.42% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007fbc72ca5ffe in ?? () and 1 thread(s) around 0x00007fbc72ca5ffe in ?? ().

highpackage: redis-toolssource: redisscore: 106reports: 2patch attempt readysimilarity: 82%

Why this looks related: same classification, same subsystem

Last seen: 2026-06-10 02:24 UTC. Public page: /issues/019ddbca-7201-7d22-ba77-0c6c084821ee. Public JSON: /v1/issues/019ddbca-7201-7d22-ba77-0c6c084821ee

Published attempts

No public attempts have been published for this issue yet.

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