Public issue detail

Runaway CPU investigation for ollama: timer churn at blkcg_maybe_throttle_current

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

highscore: 106reports: 1

Last seen: 2026-07-03 21:48 UTC. Public JSON: /v1/issues/019f29d3-54b8-7311-a948-c51a334d0d6c

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 serve
  • Why Fixer classified it this way: Timer-related syscalls or symbols dominate the sample, which suggests a wakeup timer is firing too aggressively.
  • Thread summary: thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ()
  • Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory. warning: .dynamic section for "target:<path>++.so.6" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "target:<path>" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "target:<path>" is not at the expected address (wrong library or version mismatch?)
  • Repeated loop: futex -> futex -> futex
  • Top syscalls: futex x51, epoll_pwait x2, restart_syscall x1, waitid x1
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x000055c5c39ed143 in ?? ()
0x000055c5c39a9110 in ?? ()
0x000000c000581148 in ?? ()
0x0000000000000080 in ?? ()
0x0000000000000000 in ?? ()

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 fdget

possible duplicate

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

highscore: 106reports: 2successful triagesimilarity: 99%

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

Last seen: 2026-07-03 18:33 UTC. Public page: /issues/019de4bd-5222-7312-bfda-fe64185d7301. Public JSON: /v1/issues/019de4bd-5222-7312-bfda-fe64185d7301

Runaway CPU investigation for ollama: unknown userspace loop at blkcg_maybe_throttle_current

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-07-06 10:23 UTC. Public page: /issues/019d78af-17c7-7700-aa83-b0f47d168afa. Public JSON: /v1/issues/019d78af-17c7-7700-aa83-b0f47d168afa

Runaway CPU investigation for ollama: timer churn at nvidia_poll

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-07-06 05:05 UTC. Public page: /issues/019eea9a-0584-7b50-aac5-0338cac97a48. Public JSON: /v1/issues/019eea9a-0584-7b50-aac5-0338cac97a48

Runaway CPU investigation for ollama: timer churn at __perf_event_task_sched_out

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-07-05 04:11 UTC. Public page: /issues/019f3058-0c93-77a1-9935-516cdf4cf26b. Public JSON: /v1/issues/019f3058-0c93-77a1-9935-516cdf4cf26b

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

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

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 syscall_return_via_sysret

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-07-02 15:02 UTC. Public page: /issues/019f2332-9b20-7671-8772-da74c9f83a82. Public JSON: /v1/issues/019f2332-9b20-7671-8772-da74c9f83a82

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.