Public issue detail

Runaway CPU investigation for sshd-session: unknown userspace loop at uncharge_folio

sshd-session is stuck in a likely unclassified userspace loop: 28.29% of sampled CPU passed through uncharge_folio, with repeated thread backtraces show 1 thread(s) around 0x00007f57f0c9a7d2 in ?? () from target:<path>.

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

Last seen: 2026-07-02 22:27 UTC. Public JSON: /v1/issues/019f20e6-c120-7931-9e82-74a4401b64d9

Technical snapshot

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

Representative thread backtrace

  • Command: sshd-session: gis [priv]
  • Why Fixer classified it this way: The process is demonstrably CPU-hot, but the current syscall and symbol sample does not point to a single dominant loop family yet.
  • Thread summary: thread backtraces show 1 thread(s) around 0x00007f57f0c9a7d2 in ?? () from target:<path>
  • Contention signals: event-loop-wakeups, gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory.
  • Repeated loop: restart_syscall
  • Top syscalls: restart_syscall x1
  • Package: openssh-server 1:10.3p1-1
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007f57f0c9a7d2 in ?? () from target:<path>
0x00007f57f0c9a7ed in ?? () from target:<path>
0x00007f57f0d0fd76 in poll () from target:<path>
0x00005634e0956f15 in ?? ()
0x00005634e0959264 in ?? ()
0x00005634e0931d0e in ?? ()
0x00007f57f0c31f77 in ?? () from target:<path>
0x00007f57f0c32027 in __libc_start_main () from target:<path>

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-session: unknown userspace loop at unresolved offset in libc.so.6

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 13.50% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f35fa09a7d2 in ?? () from target:<path>.

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

Last seen: 2026-06-27 21:56 UTC. Public page: /issues/019db544-ab14-73a0-b91c-7276539c4cf4. Public JSON: /v1/issues/019db544-ab14-73a0-b91c-7276539c4cf4

Runaway CPU investigation for sshd-session: unknown userspace loop at sock_poll

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through sock_poll, with repeated thread backtraces show 1 thread(s) around 0x00007f35fa09a7d2 in ?? () from target:<path>.

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-27 17:58 UTC. Public page: /issues/019dff15-4a95-7fb3-b680-40595c35ee68. Public JSON: /v1/issues/019dff15-4a95-7fb3-b680-40595c35ee68

Runaway CPU investigation for sshd-session: unknown userspace loop at __mod_node_page_state

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 24.67% of sampled CPU passed through __mod_node_page_state, with repeated thread backtraces show 1 thread(s) around 0x00007f57f0c9a7d2 in ?? () from target:<path>.

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, very similar public summary

Last seen: 2026-07-08 12:09 UTC. Public page: /issues/019f2502-84ff-79d0-bc6a-164181704a53. Public JSON: /v1/issues/019f2502-84ff-79d0-bc6a-164181704a53

Runaway CPU investigation for sshd-session: unknown userspace loop at audit_value_needs_encoding@plt

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 10.87% of sampled CPU passed through audit_value_needs_encoding@plt, with repeated thread backtraces show 1 thread(s) around 0x00007faaa249a7d2 in ?? () from target:<path>.

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-07-02 03:18 UTC. Public page: /issues/019f1fb8-ca6b-7870-b817-624c79af0149. Public JSON: /v1/issues/019f1fb8-ca6b-7870-b817-624c79af0149

Runaway CPU investigation for sshd-session: unknown userspace loop at getuid@plt

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 12.29% of sampled CPU passed through getuid@plt, with repeated thread backtraces show 1 thread(s) around 0x00007f4a7a09a7d2 in ?? () from target:<path>.

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, very similar public summary

Last seen: 2026-07-01 21:48 UTC. Public page: /issues/019f0b26-eab5-72b2-b263-744003837417. Public JSON: /v1/issues/019f0b26-eab5-72b2-b263-744003837417

Runaway CPU investigation for sshd-session: unknown userspace loop at unresolved offset in libpam.so.0.85.1

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 21.85% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f0dbde9a7d2 in ?? () from target:<path>.

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, very similar public summary

Last seen: 2026-06-27 08:47 UTC. Public page: /issues/019f056b-3325-7161-9797-4ddd63b6b535. Public JSON: /v1/issues/019f056b-3325-7161-9797-4ddd63b6b535

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.