Public issue detail

Runaway CPU investigation for sshd-auth: busy poll at unresolved offset in libc.so.6

sshd-auth is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through unresolved offset, with repeated read x3, write x2, clock_nanosleep x1.

highpackage: openssh-serversource: opensshscore: 106reports: 1

Last seen: 2026-06-13 02:15 UTC. Public JSON: /v1/issues/019eb947-ef42-7472-b634-79a6f1d97a72

Technical snapshot

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

Representative thread backtrace

  • Command: sshd-auth: root [net]
  • 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: unix_stream_read_generic
  • Hot path: unresolved offset (100.00% sampled CPU)
  • Repeated loop: clock_nanosleep -> write -> ppoll
  • Top syscalls: read x3, write x2, clock_nanosleep x1, exit_group x1
  • Package: openssh-server 1:10.3p1-1
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
unix_stream_read_generic
unix_stream_recvmsg
sock_recvmsg
sock_read_iter
vfs_read
ksys_read
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 sshd-auth: busy poll at unresolved offset in sshd-auth

possible duplicate

sshd-auth is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through unresolved offset, with repeated read x3, write x2, clock_nanosleep x1.

highpackage: openssh-serversource: opensshscore: 106reports: 2patch attempt readysimilarity: 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-13 13:44 UTC. Public page: /issues/019e1519-78c6-7813-bebb-aeb6177e1897. Public JSON: /v1/issues/019e1519-78c6-7813-bebb-aeb6177e1897

Runaway CPU investigation for sshd-auth: timer churn at unresolved offset in libcrypto.so.3

possible duplicate

sshd-auth is stuck in a likely timer churn loop: 100.00% of sampled CPU passed through unresolved offset, with repeated read x5, write x5, clock_nanosleep x2.

highpackage: openssh-serversource: opensshscore: 106reports: 2similarity: 99%

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

Last seen: 2026-06-12 00:24 UTC. Public page: /issues/019e6016-53b8-76e3-84e2-fdf4c48c1b40. Public JSON: /v1/issues/019e6016-53b8-76e3-84e2-fdf4c48c1b40

Runaway CPU investigation for sshd-auth: busy poll at unresolved offset in libcrypto.so.3

possible duplicate

sshd-auth is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through unresolved offset, with repeated read x5, write x5, clock_nanosleep x2.

highpackage: openssh-serversource: opensshscore: 106reports: 2similarity: 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-11 01:05 UTC. Public page: /issues/019e4127-e000-7341-a1bf-c93dff539a6b. Public JSON: /v1/issues/019e4127-e000-7341-a1bf-c93dff539a6b

Runaway CPU investigation for sshd-auth: busy poll at psi_group_change

possible duplicate

sshd-auth is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through psi_group_change, with repeated read x4, write x4, clock_nanosleep x2.

highpackage: openssh-serversource: opensshscore: 106reports: 1similarity: 99%

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

Last seen: 2026-06-11 03:53 UTC. Public page: /issues/019eb447-b5b7-7120-9221-da89eac7ebbb. Public JSON: /v1/issues/019eb447-b5b7-7120-9221-da89eac7ebbb

Runaway CPU investigation for sshd-auth: busy poll at default_wake_function

possible duplicate

sshd-auth is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through default_wake_function, with repeated read x3, write x2, clock_nanosleep x1.

highpackage: openssh-serversource: opensshscore: 106reports: 1similarity: 99%

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

Last seen: 2026-06-10 01:46 UTC. Public page: /issues/019eacc4-cbcf-7c52-be3d-4fd249ca28e9. Public JSON: /v1/issues/019eacc4-cbcf-7c52-be3d-4fd249ca28e9

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

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

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

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

Last seen: 2026-06-13 13:51 UTC. Public page: /issues/019dc199-535d-7c90-9b68-f6459f9c134d. Public JSON: /v1/issues/019dc199-535d-7c90-9b68-f6459f9c134d

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.