Public issue detail

Runaway CPU investigation for ollama: timer churn at __update_load_avg_se

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

highsource: linuxscore: 106reports: 1

Last seen: 2026-05-18 06:51 UTC. Public JSON: /v1/issues/019e39a7-ad06-7663-be24-fb548be8d52d

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 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 __rseq_handle_notify_resume

possible duplicate

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

highsource: linuxscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-05-18 17:41 UTC. Public page: /issues/019e2167-62bd-7611-a216-57737a2b1914. Public JSON: /v1/issues/019e2167-62bd-7611-a216-57737a2b1914

Runaway CPU investigation for ollama: timer churn at exit_to_user_mode_loop

possible duplicate

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

highsource: linuxscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-05-18 13:58 UTC. Public page: /issues/019e3b2e-7ef6-7b11-9c4c-6f384a55501d. Public JSON: /v1/issues/019e3b2e-7ef6-7b11-9c4c-6f384a55501d

Runaway CPU investigation for ollama: unknown userspace loop at __update_load_avg_se

possible duplicate

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

highsource: linuxscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-05-18 02:12 UTC. Public page: /issues/019db12c-6407-7881-964e-6788195ec743. Public JSON: /v1/issues/019db12c-6407-7881-964e-6788195ec743

Runaway CPU investigation for ollama: timer churn at __update_load_avg_cfs_rq

possible duplicate

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

highsource: linuxscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-05-15 22:06 UTC. Public page: /issues/019e263f-66da-7ba1-ad74-458b8260e4a6. Public JSON: /v1/issues/019e263f-66da-7ba1-ad74-458b8260e4a6

Runaway CPU investigation for ollama: timer churn at timerqueue_add

possible duplicate

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

highsource: linuxscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-05-15 17:46 UTC. Public page: /issues/019e2c8c-7197-7c42-bd9a-8d239b7918c0. Public JSON: /v1/issues/019e2c8c-7197-7c42-bd9a-8d239b7918c0

Runaway CPU investigation for ollama: timer churn at _raw_spin_lock_irqsave

possible duplicate

ollama is stuck in a likely timer churn loop: 25.00% 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 ?? ().

highsource: linuxscore: 106reports: 1successful triagesimilarity: 99%

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

Last seen: 2026-05-15 14:22 UTC. Public page: /issues/019dd4d2-521a-7bc2-8b35-4929317528f3. Public JSON: /v1/issues/019dd4d2-521a-7bc2-8b35-4929317528f3

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.