Public issue detail

Runaway CPU investigation for ollama: busy poll at __pollwait

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

highscore: 106reports: 1successful triage

Last seen: 2026-06-07 19:31 UTC. Public JSON: /v1/issues/019d6e22-cfed-7f90-bd09-7cf360f99381

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 08:37 UTCvalidation: ready

ollama likely remains stuck in a busy-poll loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90935 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 37847
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 0x00007fd24d6a5ffe in ?? () from target:<path> and 1 thread(s) around 0x0000557c74530143 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 x30, restart_syscall x3, epoll_pwait x1
Kernel: 6.17.10+deb14-amd64
Distribution: debian

0x00007fd24d6a5ffe in ?? () from target:<path>
0x00007fd24d69a7a4 in ?? () from target:<path>
0x00007fd24d69a7ed in ?? () from target:<path>
0x00007fd24d70fd76 in poll () from target:<path>
0x00007fd1e1a7644f in ?? () from target:<path>
0x00007fd1e1b3a80f in ?? () from target:<path>
0x00007fd1e1a6e143 in ?? () from target:<path>
0x00007fd24d69dda9 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: 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 triagesimilarity: 99%

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

Last seen: 2026-06-10 04:35 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 dequeue_entity

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-06-07 22:00 UTC. Public page: /issues/019db4dd-c68c-72b1-b12f-90ce87f6c4ba. Public JSON: /v1/issues/019db4dd-c68c-72b1-b12f-90ce87f6c4ba

Runaway CPU investigation for ollama: busy poll at sched_clock_cpu

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-06-07 11:40 UTC. Public page: /issues/019ea17c-c5c2-7922-8907-8550a45ed847. Public JSON: /v1/issues/019ea17c-c5c2-7922-8907-8550a45ed847

Runaway CPU investigation for ollama: busy poll at do_sys_poll

possible duplicate

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

highscore: 106reports: 1similarity: 98%

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

Last seen: 2026-06-09 04:10 UTC. Public page: /issues/019d9be2-688e-7322-8c64-16858641b819. Public JSON: /v1/issues/019d9be2-688e-7322-8c64-16858641b819

Runaway CPU investigation for ollama: busy poll at __schedule

possible duplicate

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

highscore: 106reports: 1successful triagesimilarity: 95%

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

Last seen: 2026-06-10 05:50 UTC. Public page: /issues/019e07ce-c238-7970-a71b-590759f50bd9. Public JSON: /v1/issues/019e07ce-c238-7970-a71b-590759f50bd9

Runaway CPU investigation for ollama: busy poll at __x64_sys_poll

possible duplicate

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

highscore: 106reports: 1similarity: 95%

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

Last seen: 2026-06-08 22:14 UTC. Public page: /issues/019ea91a-8f4d-7612-b7f0-ea5dfc3e6095. Public JSON: /v1/issues/019ea91a-8f4d-7612-b7f0-ea5dfc3e6095

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 90935 has no repo root, package name, or source package

state: readycreated: 2026-05-20 08:37 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.