Public issue detail

Runaway CPU investigation for ollama: busy poll at dequeue_entity

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: 1

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

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 37749
  • 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 0x00007f8964d81ffe in ?? () from target:<path> and 1 thread(s) around 0x0000564186607143 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 x32, restart_syscall x3, <... poll resumed>) = 0 x1
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007f8964d81ffe in ?? () from target:<path>
0x00007f8964d767a4 in ?? () from target:<path>
0x00007f8964d767ed in ?? () from target:<path>
0x00007f8964debd76 in poll () from target:<path>
0x00007f8891c7644f in ?? () from target:<path>
0x00007f8891d3a80f in ?? () from target:<path>
0x00007f8891c6e143 in ?? () from target:<path>
0x00007f8964d79da9 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 dequeue_entities

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-06-09 02:35 UTC. Public page: /issues/019d9b8f-fb5f-7ce2-bab6-8e354bc2f457. Public JSON: /v1/issues/019d9b8f-fb5f-7ce2-bab6-8e354bc2f457

Runaway CPU investigation for ollama: busy poll at __pollwait

possible duplicate

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 triagesimilarity: 99%

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

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

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

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

Last seen: 2026-06-10 03:39 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 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: 93%

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 __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: 90%

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

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

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

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

Published attempts

No public attempts have been published for this issue yet.

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