Public issue detail

Runaway CPU investigation for ollama: busy poll at check_stack_object

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

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

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 34783
  • 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 0x00007f5ea9bb14be in ?? () from target:<path> and 1 thread(s) around 0x000055b0b942d143 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 x61, poll x50, nanosleep x24, getpid x11
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007f5ea9bb14be in ?? () from target:<path>
0x00007f5ea9ba5c84 in ?? () from target:<path>
0x00007f5ea9ba5ccd in ?? () from target:<path>
0x00007f5ea9c1ac76 in poll () from target:<path>
0x00007f5dd687644f in ?? () from target:<path>
0x00007f5dd693a80f in ?? () from target:<path>
0x00007f5dd686e143 in ?? () from target:<path>
0x00007f5ea9ba9289 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: unknown userspace loop at check_stack_object

possible duplicate

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

highscore: 106reports: 1similarity: 96%

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

Last seen: 2026-06-30 10:04 UTC. Public page: /issues/019d59f3-0483-7190-8dcd-12a3a490ab48. Public JSON: /v1/issues/019d59f3-0483-7190-8dcd-12a3a490ab48

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

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

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

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

possible duplicate

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

highscore: 106reports: 1similarity: 72%

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

Last seen: 2026-07-03 07:58 UTC. Public page: /issues/019d923e-9063-7b13-831f-2476cfee31b3. Public JSON: /v1/issues/019d923e-9063-7b13-831f-2476cfee31b3

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.