Public issue detail

Runaway CPU investigation for ollama: timer churn at __hrtimer_setup

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

Last seen: 2026-06-04 11:13 UTC. Public JSON: /v1/issues/019d85a7-37c6-7671-8000-ffbb4d39e629

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 unresolved offset in libggml-cpu-skylakex.so

possible duplicate

ollama is stuck in a likely timer churn loop: 22.80% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c397a50e 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-06-05 20:59 UTC. Public page: /issues/019e152a-ab3c-7eb2-9b23-bb82affe5be9. Public JSON: /v1/issues/019e152a-ab3c-7eb2-9b23-bb82affe5be9

Runaway CPU investigation for ollama: timer churn at fdget

possible duplicate

ollama is stuck in a likely timer churn loop: 25.00% 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-06-04 05:02 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 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: 99%

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

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

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: 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-06-05 04:27 UTC. Public page: /issues/019d923e-9063-7b13-831f-2476cfee31b3. Public JSON: /v1/issues/019d923e-9063-7b13-831f-2476cfee31b3

Runaway CPU investigation for ollama: timer churn at do_sys_poll

possible duplicate

ollama is stuck in a likely timer churn loop: 25.00% of sampled CPU passed through do_sys_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-06-04 06:35 UTC. Public page: /issues/019dde46-63b9-7120-ad03-592b7c01a22b. Public JSON: /v1/issues/019dde46-63b9-7120-ad03-592b7c01a22b

Published attempts

No public attempts have been published for this issue yet.