Public issue detail

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

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

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

Last seen: 2026-06-12 00:05 UTC. Public JSON: /v1/issues/019eb830-1096-7f12-805b-f3812918b4c3

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 0x00007f03a509a7d2 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
0x00007f03a509a7d2 in ?? () from target:<path>
0x00007f03a509a7ed in ?? () from target:<path>
0x00007f03a510fd76 in poll () from target:<path>
0x0000556177c7ef15 in ?? ()
0x0000556177c81264 in ?? ()
0x0000556177c59d0e in ?? ()
0x00007f03a5031f77 in ?? () from target:<path>
0x00007f03a5032027 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: 21.05% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f35c729a7d2 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-13 07:40 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 kfree

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 28.13% of sampled CPU passed through kfree, with repeated thread backtraces show 1 thread(s) around 0x00007f35c729a7d2 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, very similar public summary

Last seen: 2026-06-12 05:47 UTC. Public page: /issues/019e0f77-fd2f-7ef3-9c33-5cae8af4813f. Public JSON: /v1/issues/019e0f77-fd2f-7ef3-9c33-5cae8af4813f

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

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 7.41% of sampled CPU passed through memset_orig, with repeated thread backtraces show 1 thread(s) around 0x00007f03a509a7d2 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, very similar public summary

Last seen: 2026-06-11 19:18 UTC. Public page: /issues/019dfb88-84b0-7961-b77d-94d71b584731. Public JSON: /v1/issues/019dfb88-84b0-7961-b77d-94d71b584731

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

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 16.53% of sampled CPU passed through mas_wr_store_type, with repeated thread backtraces show 1 thread(s) around 0x00007f35c729a7d2 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-06-13 13:51 UTC. Public page: /issues/019ebb64-896d-7641-b46b-62fc8b8053d3. Public JSON: /v1/issues/019ebb64-896d-7641-b46b-62fc8b8053d3

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

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 10.54% of sampled CPU passed through mas_walk, with repeated thread backtraces show 1 thread(s) around 0x00007f35c729a7d2 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-12 10:14 UTC. Public page: /issues/019eba70-7969-7b93-ad03-2faff35eac5f. Public JSON: /v1/issues/019eba70-7969-7b93-ad03-2faff35eac5f

Runaway CPU investigation for sshd-session: unknown userspace loop at unresolved offset in ld-linux-x86-64.so.2

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 19.96% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f6cc509a7d2 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-11 01:05 UTC. Public page: /issues/019eaf7a-f4e0-7222-a6a7-9e5e24788c96. Public JSON: /v1/issues/019eaf7a-f4e0-7222-a6a7-9e5e24788c96

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.