Public issue detail

Runaway CPU investigation for ollama: busy poll at eventfd_poll

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

highscore: 106reports: 1successful triage

Last seen: 2026-06-25 17:34 UTC. Public JSON: /v1/issues/019e05e2-de56-7892-b298-bfd1dbb58877

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 21:28 UTCvalidation: ready

ollama likely remains stuck in a busy-poll loop. A diagnosis report was created even though no patchable workspace was available: opportunity 91325 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 34805
  • 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 0x00007f6e4cbafffe in ?? () from target:<path> and 1 thread(s) around 0x000055f82de82143 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: futex x57, poll x50, getpid x4, rt_sigreturn x4
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007f6e4cbafffe in ?? () from target:<path>
0x00007f6e4cba47a4 in ?? () from target:<path>
0x00007f6e4cba47ed in ?? () from target:<path>
0x00007f6e4cc19d76 in poll () from target:<path>
0x00007f6ded67644f in ?? () from target:<path>
0x00007f6ded73a80f in ?? () from target:<path>
0x00007f6ded66e143 in ?? () from target:<path>
0x00007f6e4cba7da9 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: 95%

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

Last seen: 2026-07-10 02:05 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: 87%

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

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

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

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 postgres: busy poll at next_uptodate_folio

possible duplicate

postgres is stuck in a likely busy poll loop: 20.28% of sampled CPU passed through next_uptodate_folio, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

highpackage: postgresql-18source: postgresql-18score: 106reports: 2successful triagesimilarity: 76%

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

Last seen: 2026-06-27 02:02 UTC. Public page: /issues/019dd9b3-4d4e-73f0-86bb-bf7e642a5785. Public JSON: /v1/issues/019dd9b3-4d4e-73f0-86bb-bf7e642a5785

Runaway CPU investigation for smtpd: busy poll at unix_maybe_add_creds

possible duplicate

smtpd is stuck in a likely busy poll loop: 14.11% of sampled CPU passed through unix_maybe_add_creds, with repeated thread backtraces show 1 thread(s) around 0x00007f529799e7d2 in ?? () from target:<path>.

highpackage: postfixsource: postfixscore: 106reports: 1similarity: 76%

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

Last seen: 2026-07-04 06:14 UTC. Public page: /issues/019ec5c3-2f99-7ea0-9bcc-7718d776a285. Public JSON: /v1/issues/019ec5c3-2f99-7ea0-9bcc-7718d776a285

Runaway CPU investigation for redis-check-rdb: busy poll at update_curr

possible duplicate

redis-check-rdb is stuck in a likely busy poll loop: 4.80% of sampled CPU passed through update_curr, with repeated thread backtraces show 1 thread(s) around 0x00007f89688a74be in ?? () and 1 thread(s) around 0x00007f89688a74be in ?? ().

highpackage: redis-toolssource: redisscore: 106reports: 1similarity: 74%

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

Last seen: 2026-07-07 12:41 UTC. Public page: /issues/019f3c77-d8db-79f2-96d6-1595084d836f. Public JSON: /v1/issues/019f3c77-d8db-79f2-96d6-1595084d836f

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

state: readycreated: 2026-05-22 21:28 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.