Public issue detail

Runaway CPU investigation for ollama: unknown userspace loop at blkcg_maybe_throttle_current

ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through blkcg_maybe_throttle_current, 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-06 10:23 UTC. Public JSON: /v1/issues/019d78af-17c7-7700-aa83-b0f47d168afa

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 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 _raw_spin_trylock

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through _raw_spin_trylock, 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 08:15 UTC. Public page: /issues/019ded48-a351-7db1-b2cd-e2a5a99f7943. Public JSON: /v1/issues/019ded48-a351-7db1-b2cd-e2a5a99f7943

Runaway CPU investigation for ollama: unknown userspace loop at do_sys_poll

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through do_sys_poll, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c397a50e 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 07:19 UTC. Public page: /issues/019d3e52-af65-7fc0-8bde-cb0d66558df4. Public JSON: /v1/issues/019d3e52-af65-7fc0-8bde-cb0d66558df4

Runaway CPU investigation for ollama: unknown userspace loop at poll_freewait

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-07-06 03:14 UTC. Public page: /issues/019ec73a-660b-7853-9a32-c005b0b10854. Public JSON: /v1/issues/019ec73a-660b-7853-9a32-c005b0b10854

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.