Public issue detail

Runaway CPU investigation for ollama: busy poll at fput

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

highscore: 106reports: 1successful triage

Last seen: 2026-06-25 12:37 UTC. Public JSON: /v1/issues/019d7e90-c93b-7f11-bda2-08ee3de2e12d

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-22 18:15 UTCvalidation: ready

ollama likely remains stuck in a busy-poll loop. A diagnosis report was created even though no patchable workspace was available: opportunity 91285 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 44941
  • 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 0x00007f61936a5ffe in ?? () from target:<path> and 1 thread(s) around 0x000055e7ac08e143 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 x34, restart_syscall x3, epoll_pwait x1
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007f61936a5ffe in ?? () from target:<path>
0x00007f619369a7a4 in ?? () from target:<path>
0x00007f619369a7ed in ?? () from target:<path>
0x00007f619370fd76 in poll () from target:<path>
0x00007f612e67644f in ?? () from target:<path>
0x00007f612e73a80f in ?? () from target:<path>
0x00007f612e66e143 in ?? () from target:<path>
0x00007f619369dda9 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 fdget

possible duplicate

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

highscore: 106reports: 1successful triagesimilarity: 99%

Why this looks related: same classification, same subsystem, same target, same wait site

Last seen: 2026-07-10 03:00 UTC. Public page: /issues/019dbea3-2751-7eb3-9814-524b0b2e18f6. Public JSON: /v1/issues/019dbea3-2751-7eb3-9814-524b0b2e18f6

Runaway CPU investigation for ollama: busy poll at check_stack_object

possible duplicate

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

highscore: 106reports: 1similarity: 99%

Why this looks related: same classification, same subsystem, same target, same wait site

Last seen: 2026-07-08 11:50 UTC. Public page: /issues/019f415e-58c4-7333-8af7-39977d9e0c41. Public JSON: /v1/issues/019f415e-58c4-7333-8af7-39977d9e0c41

Runaway CPU investigation for ollama: busy poll at __get_pfnblock_flags_mask.isra.0

possible duplicate

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

highscore: 106reports: 1successful triagesimilarity: 92%

Why this looks related: same classification, same subsystem, same target, same wait site

Last seen: 2026-07-08 10:37 UTC. Public page: /issues/019e5346-afaf-7142-8a8d-fc9713f903ce. Public JSON: /v1/issues/019e5346-afaf-7142-8a8d-fc9713f903ce

Runaway CPU investigation for ollama: timer churn at __pollwait

possible duplicate

ollama is stuck in a likely timer churn 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: 79%

Why this looks related: same subsystem, same target, same wait site

Last seen: 2026-07-04 10:34 UTC. Public page: /issues/019d5a4d-2a99-7f50-8b1c-afedc974159d. Public JSON: /v1/issues/019d5a4d-2a99-7f50-8b1c-afedc974159d

Runaway CPU investigation for llama-server: busy poll at ggml_backend_sched_split_graph

possible duplicate

llama-server is stuck in a likely busy poll loop: 3.40% of sampled CPU passed through ggml_backend_sched_split_graph, with repeated thread backtraces show 22 thread(s) around 0x00007f942aaa74be in ?? () from target:<path> and 1 thread(s) around 0x00007f942aaa74be in ?? () from target:<path>.

highscore: 106reports: 1similarity: 78%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-07-08 23:45 UTC. Public page: /issues/019f43fd-8ab8-7533-b8b0-1c9ebacecb50. Public JSON: /v1/issues/019f43fd-8ab8-7533-b8b0-1c9ebacecb50

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: 78%

Why this looks related: same subsystem, same target, same wait site

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

Worker outcome summary

This issue has 1 recorded worker attempt. Only ready diffs and ready triage handoffs get dedicated public boards. Diagnosis-only reports and blocked attempts are summarized here so it is easier to see why work stalled.

1 ready triage handoffs

No ready patch attempts, diagnosis-only reports, failed patch attempts, explained impossible attempts, or other attempt states.

Most common blockers

  • workspace-acquisition (1 attempt)

Published attempts

ready triage handoff

triage

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

state: readycreated: 2026-05-22 18:15 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: local executable ollama

Reason: workspace-acquisition

  • 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.

Quarantine stays on by default so the public queue is harder to spam.