Public issue detail

Runaway CPU investigation for ollama: busy poll at __alloc_frozen_pages_noprof

ollama is stuck in a likely busy poll loop: 25.00% of sampled CPU passed through __alloc_frozen_pages_noprof, with repeated nanosleep x62, read x52, futex x45.

highscore: 106reports: 1successful triage

Last seen: 2026-06-26 03:30 UTC. Public JSON: /v1/issues/019d70ae-1745-7a61-bf99-23291ddb1a40

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-23 10:14 UTCvalidation: ready

ollama likely remains stuck in a busy-poll loop. A diagnosis report was created even though no patchable workspace was available: opportunity 91516 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 45943
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.
Wait site: futex_do_wait
Hot path: __alloc_frozen_pages_noprof (25.00% sampled CPU)
Repeated loop: poll -> poll -> poll
Top syscalls: nanosleep x62, read x52, futex x45, poll x37
Kernel: 6.17.10+deb14-amd64
Distribution: debian

futex_do_wait
__futex_wait
futex_wait
do_futex
__x64_sys_futex
do_syscall_64
entry_SYSCALL_64_after_hwframe

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: timer churn at __alloc_frozen_pages_noprof

possible duplicate

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

highscore: 106reports: 1successful triagesimilarity: 97%

Why this looks related: same stack or hot path signature, same subsystem, same target, same wait site

Last seen: 2026-07-03 13:09 UTC. Public page: /issues/019e28d6-4dcd-7fe3-9a41-ee13f6e241c2. Public JSON: /v1/issues/019e28d6-4dcd-7fe3-9a41-ee13f6e241c2

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

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

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

possible duplicate

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

highscore: 106reports: 1successful triagesimilarity: 77%

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

Last seen: 2026-07-02 02:41 UTC. Public page: /issues/019d62e0-f9a9-7d30-9b0f-5b0b64ab3425. Public JSON: /v1/issues/019d62e0-f9a9-7d30-9b0f-5b0b64ab3425

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

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

possible duplicate

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

highscore: 106reports: 1successful triagesimilarity: 71%

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

Last seen: 2026-06-29 13:59 UTC. Public page: /issues/019e3a1e-754b-7412-98c3-2dd07204d546. Public JSON: /v1/issues/019e3a1e-754b-7412-98c3-2dd07204d546

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

state: readycreated: 2026-05-23 10:14 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.