Public issue detail

Runaway CPU investigation for ollama: busy poll at sched_clock_cpu

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

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

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 33555
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 0x00007ff1342a5ffe in ?? () from target:<path> and 1 thread(s) around 0x000055f072b1a143 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 x49, futex x30, restart_syscall x3, epoll_pwait x1
Kernel: 6.17.10+deb14-amd64
Distribution: debian

0x00007ff1342a5ffe in ?? () from target:<path>
0x00007ff13429a7a4 in ?? () from target:<path>
0x00007ff13429a7ed in ?? () from target:<path>
0x00007ff13430fd76 in poll () from target:<path>
0x00007ff0d127644f in ?? () from target:<path>
0x00007ff0d133a80f in ?? () from target:<path>
0x00007ff0d126e143 in ?? () from target:<path>
0x00007ff13429dda9 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 __rcu_read_lock

possible duplicate

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

highscore: 106reports: 2successful triagesimilarity: 99%

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

Last seen: 2026-06-08 10:57 UTC. Public page: /issues/019e5fd1-d5f7-7c63-9423-e137be5b35f4. Public JSON: /v1/issues/019e5fd1-d5f7-7c63-9423-e137be5b35f4

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

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

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 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, same wait site

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

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

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

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

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 __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, very similar public summary

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

Published attempts

No public attempts have been published for this issue yet.