Public issue detail

Runaway CPU investigation for ollama: unknown userspace loop at __rseq_handle_notify_resume

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through __rseq_handle_notify_resume, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 1

Last seen: 2026-07-02 23:59 UTC. Public JSON: /v1/issues/019d7622-40b3-7f01-bec6-baec12d05e11

Technical snapshot

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

Representative thread backtrace

  • Command: /usr/local/bin/ollama serve
  • 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 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ()
  • Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory. warning: .dynamic section for "target:<path>++.so.6" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "target:<path>" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "target:<path>" is not at the expected address (wrong library or version mismatch?)
  • Repeated loop: futex -> futex -> futex
  • Top syscalls: futex x51, epoll_pwait x2, restart_syscall x1, waitid x1
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x000055c5c39ed143 in ?? ()
0x000055c5c39a9110 in ?? ()
0x000000c000581148 in ?? ()
0x0000000000000080 in ?? ()
0x0000000000000000 in ?? ()

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 ollama: unknown userspace loop at __free_one_page

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through __free_one_page, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-07-07 21:30 UTC. Public page: /issues/019dba91-e079-7393-8193-774ba6aa0b53. Public JSON: /v1/issues/019dba91-e079-7393-8193-774ba6aa0b53

Runaway CPU investigation for ollama: unknown userspace loop at _raw_spin_lock_irqsave

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through _raw_spin_lock_irqsave, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-07-07 19:59 UTC. Public page: /issues/019d780b-a338-7841-9ba2-3bf6ad9294de. Public JSON: /v1/issues/019d780b-a338-7841-9ba2-3bf6ad9294de

Runaway CPU investigation for ollama: unknown userspace loop at fdget

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through fdget, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-07-07 14:12 UTC. Public page: /issues/019dbcec-f056-7ae0-bc8f-d6d03bb07fcc. Public JSON: /v1/issues/019dbcec-f056-7ae0-bc8f-d6d03bb07fcc

Runaway CPU investigation for ollama: unknown userspace loop at fput

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 26.50% of sampled CPU passed through fput, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-07-06 09:10 UTC. Public page: /issues/019dbb1d-f3d1-79d0-be89-356d1cb05fde. Public JSON: /v1/issues/019dbb1d-f3d1-79d0-be89-356d1cb05fde

Runaway CPU investigation for ollama: unknown userspace loop at dequeue_entities

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through dequeue_entities, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-07-06 04:09 UTC. Public page: /issues/019df910-cc70-7c62-addd-c380bd22f920. Public JSON: /v1/issues/019df910-cc70-7c62-addd-c380bd22f920

Runaway CPU investigation for ollama: unknown userspace loop at __pollwait

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through __pollwait, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-07-06 02:01 UTC. Public page: /issues/019dd09e-61b4-7ed0-a93f-a3480ebc9b11. Public JSON: /v1/issues/019dd09e-61b4-7ed0-a93f-a3480ebc9b11

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.