Public issue detail

Runaway CPU investigation for ollama: timer churn at __rmqueue_pcplist

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

highscore: 106reports: 1

Last seen: 2026-06-29 20:41 UTC. Public JSON: /v1/issues/019d67fc-7f93-7fa3-8351-8427e8a5f655

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?)
  • Repeated loop: lseek -> lseek -> lseek
  • Top syscalls: futex x780, nanosleep x525, lseek x307, read x305
  • 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: timer churn at change_protection

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-07-06 13:26 UTC. Public page: /issues/019f3769-e87c-71f1-b3d0-8b94f43b3ff6. Public JSON: /v1/issues/019f3769-e87c-71f1-b3d0-8b94f43b3ff6

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 __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 __alloc_frozen_pages_noprof

possible duplicate

ollama is stuck in a likely timer churn loop: 25.00% of sampled CPU passed through __alloc_frozen_pages_noprof, 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-03 13:09 UTC. Public page: /issues/019e28d6-4dcd-7fe3-9a41-ee13f6e241c2. Public JSON: /v1/issues/019e28d6-4dcd-7fe3-9a41-ee13f6e241c2

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

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

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.