Public issue detail

Runaway CPU investigation for ollama: timer churn at _raw_spin_unlock_irqrestore

ollama is stuck in a likely timer churn loop: 25.00% of sampled CPU passed through _raw_spin_unlock_irqrestore, 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-13 07:03 UTC. Public JSON: /v1/issues/019daf3f-0b0f-75f3-91da-f5f39f0cbb98

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: futex -> futex -> futex
  • Top syscalls: futex x96, nanosleep x32, getpid x9, rt_sigreturn x9
  • 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 __hrtimer_setup

possible duplicate

ollama is stuck in a likely timer churn loop: 25.00% of sampled CPU passed through __hrtimer_setup, 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-06-13 13:33 UTC. Public page: /issues/019d85a7-37c6-7671-8000-ffbb4d39e629. Public JSON: /v1/issues/019d85a7-37c6-7671-8000-ffbb4d39e629

Runaway CPU investigation for ollama: timer churn at dequeue_entity

possible duplicate

ollama is stuck in a likely timer churn loop: 25.00% of sampled CPU passed through dequeue_entity, 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-06-12 06:06 UTC. Public page: /issues/019da1a9-e836-71e2-9dea-90f7a74a33f6. Public JSON: /v1/issues/019da1a9-e836-71e2-9dea-90f7a74a33f6

Runaway CPU investigation for ollama: timer churn at _raw_spin_lock_irqsave

possible duplicate

ollama is stuck in a likely timer churn loop: 33.33% of sampled CPU passed through _raw_spin_lock_irqsave, 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-06-11 06:41 UTC. Public page: /issues/019dd4d2-521a-7bc2-8b35-4929317528f3. Public JSON: /v1/issues/019dd4d2-521a-7bc2-8b35-4929317528f3

Runaway CPU investigation for ollama: timer churn at fput

possible duplicate

ollama is stuck in a likely timer churn loop: 50.00% of sampled CPU passed through fput, 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-06-06 17:41 UTC. Public page: /issues/019e1d17-4102-7990-9fc5-5b7e6c0f318e. Public JSON: /v1/issues/019e1d17-4102-7990-9fc5-5b7e6c0f318e

Runaway CPU investigation for ollama: unknown userspace loop at _raw_spin_unlock_irqrestore

possible duplicate

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

highscore: 106reports: 1successful triagesimilarity: 98%

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

Last seen: 2026-06-12 20:15 UTC. Public page: /issues/019d81f7-e601-75f3-a77f-f63b774d35e0. Public JSON: /v1/issues/019d81f7-e601-75f3-a77f-f63b774d35e0

Runaway CPU investigation for ollama: timer churn at unresolved offset in ollama

possible duplicate

ollama is stuck in a likely timer churn loop: 10.18% of sampled CPU passed through unresolved offset, 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 classification, same subsystem, same target, same wait site

Last seen: 2026-06-07 16:07 UTC. Public page: /issues/019de62e-e5d8-7170-a655-07d9eed9548f. Public JSON: /v1/issues/019de62e-e5d8-7170-a655-07d9eed9548f

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.