Public issue detail

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

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

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

Last seen: 2026-06-10 02:05 UTC. Public JSON: /v1/issues/019ea95e-8037-7fa1-8a43-e6761943059e

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 0x00007f97df09a7d2 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

0x00007f97df09a7d2 in ?? () from target:<path>
0x00007f97df09a7ed in ?? () from target:<path>
0x00007f97df10fd76 in poll () from target:<path>
0x0000557c9f99af15 in ?? ()
0x0000557c9f99d264 in ?? ()
0x0000557c9f975d0e in ?? ()
0x00007f97df031f77 in ?? () from target:<path>
0x00007f97df032027 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: 19.66% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f68c0e9a7d2 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-07 21:04 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 xas_find

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 27.43% of sampled CPU passed through xas_find, with repeated thread backtraces show 1 thread(s) around 0x00007f97df09a7d2 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-08 22:14 UTC. Public page: /issues/019ea896-8735-7d91-84b8-38102d5ba77f. Public JSON: /v1/issues/019ea896-8735-7d91-84b8-38102d5ba77f

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

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 16.65% of sampled CPU passed through copy_page_range, with repeated thread backtraces show 1 thread(s) around 0x00007f9aee09a7d2 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-08 18:36 UTC. Public page: /issues/019e676a-fef9-72e2-b67e-a26d1e8f0674. Public JSON: /v1/issues/019e676a-fef9-72e2-b67e-a26d1e8f0674

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

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 21.47% of sampled CPU passed through _raw_write_unlock_bh, with repeated thread backtraces show 1 thread(s) around 0x00007f68c0e9a7d2 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-08 03:15 UTC. Public page: /issues/019ea3f7-fd44-7bc0-be26-cb07d069a2cf. Public JSON: /v1/issues/019ea3f7-fd44-7bc0-be26-cb07d069a2cf

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

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 28.16% of sampled CPU passed through page_counter_uncharge, with repeated thread backtraces show 1 thread(s) around 0x00007f87d549a7d2 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-07 05:47 UTC. Public page: /issues/019e9d73-04f4-70a1-9cfe-bacd61f5c8f0. Public JSON: /v1/issues/019e9d73-04f4-70a1-9cfe-bacd61f5c8f0

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

possible duplicate

sshd-session is stuck in a likely unclassified userspace loop: 27.91% of sampled CPU passed through xa_load, with repeated thread backtraces show 1 thread(s) around 0x00007f87d549a7d2 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-06 14:41 UTC. Public page: /issues/019e9c30-56f2-7462-8d48-73426363b601. Public JSON: /v1/issues/019e9c30-56f2-7462-8d48-73426363b601

Published attempts

No public attempts have been published for this issue yet.