Public issue detail

Runaway CPU investigation for ollama: busy poll at fdget

ollama is stuck in a likely busy poll loop: 33.33% of sampled CPU passed through fdget, with repeated thread backtraces show 2 thread(s) around 0x00007f725ddafffe in ?? () from target:<path> and 1 thread(s) around 0x000055ccb1c57143 in ?? ().

highscore: 106reports: 1successful triage

Last seen: 2026-06-10 04:35 UTC. Public JSON: /v1/issues/019dbea3-2751-7eb3-9814-524b0b2e18f6

Successful triage

Fixer did not find an honest diff-backed change in this source tree. Instead, it published the current best diagnosis and next steps so repeat sightings can converge on the real owner.

best triagecreated: 2026-05-20 20:12 UTCvalidation: ready

ollama likely remains stuck in a busy-poll loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90987 has no repo root, package name, or source package

Likely owner

local executable ollama

Reason: workspace-acquisition

Next steps

Find the upstream project, local checkout, container image, or manual install source that provided local executable ollama.
Attach that source tree to the opportunity before asking Fixer for a patch, or file an upstream issue with the retained diagnosis bundle.
Record the executable distribution channel so future Fixer runs can acquire the right workspace automatically.

Browse successful triage

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 runner --ollama-engine --model /usr/share/ollama/.ollama/models/blobs/sha256-797b70c4edf85907fe0a49eb85811256f65fa0f7bf52166b147fd16be2be4662 --port 39389
Why Fixer classified it this way: The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.
Thread summary: thread backtraces show 2 thread(s) around 0x00007f725ddafffe in ?? () from target:<path> and 1 thread(s) around 0x000055ccb1c57143 in ?? ()
Contention signals: event-loop-wakeups, gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory.
Repeated loop: poll -> poll -> poll
Top syscalls: poll x50, futex x29, restart_syscall x3, epoll_pwait x1
Kernel: 6.17.10+deb14-amd64
Distribution: debian

0x00007f725ddafffe in ?? () from target:<path>
0x00007f725dda47a4 in ?? () from target:<path>
0x00007f725dda47ed in ?? () from target:<path>
0x00007f725de19d76 in poll () from target:<path>
0x00007f71fa27644f in ?? () from target:<path>
0x00007f71fa33a80f in ?? () from target:<path>
0x00007f71fa26e143 in ?? () from target:<path>
0x00007f725dda7da9 in ?? () 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 ollama: busy poll at __rcu_read_lock

possible duplicate

ollama is stuck in a likely busy poll loop: 25.00% of sampled CPU passed through __rcu_read_lock, with repeated thread backtraces show 2 thread(s) around 0x00007f0c37aa5ffe in ?? () from target:<path> and 1 thread(s) around 0x000055b0cb3c1143 in ?? ().

highscore: 106reports: 2successful triagesimilarity: 99%