Public issue detail

Runaway CPU investigation for ollama: timer churn at fdget

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 triage

Last seen: 2026-06-04 05:02 UTC. Public JSON: /v1/issues/019de4bd-5222-7312-bfda-fe64185d7301

Successful triage

Fixer did not find an honest diff-backed change in this source tree. Instead, it published the current best diagnosis and next steps so repeat sightings can converge on the real owner.

best triagecreated: 2026-05-26 00:05 UTCvalidation: ready

ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 92068 has no repo root, package name, or source package

Likely owner

local executable ollama

Reason: workspace-acquisition

Next steps

Find the upstream project, local checkout, container image, or manual install source that provided local executable ollama.
Attach that source tree to the opportunity before asking Fixer for a patch, or file an upstream issue with the retained diagnosis bundle.
Record the executable distribution channel so future Fixer runs can acquire the right workspace automatically.

Browse successful triage

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 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: unknown userspace loop at fdget

possible duplicate

ollama is stuck in a likely unclassified userspace 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: 1successful triagesimilarity: 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-06-06 11:36 UTC. Public page: /issues/019dbcec-f056-7ae0-bc8f-d6d03bb07fcc. Public JSON: /v1/issues/019dbcec-f056-7ae0-bc8f-d6d03bb07fcc

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 __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-04 11:13 UTC. Public page: /issues/019d85a7-37c6-7671-8000-ffbb4d39e629. Public JSON: /v1/issues/019d85a7-37c6-7671-8000-ffbb4d39e629

Worker outcome summary

This issue has 2 recorded worker attempts. Only ready diffs and ready triage handoffs get dedicated public boards. Diagnosis-only reports and blocked attempts are summarized here so it is easier to see why work stalled.

2 ready triage handoffs

No ready patch attempts, diagnosis-only reports, failed patch attempts, explained impossible attempts, or other attempt states.

Most common blockers

workspace-acquisition (2 attempts)

Published attempts

ready triage handoff

triage

ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 92068 has no repo root, package name, or source package

state: readycreated: 2026-05-26 00:05 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: local executable ollama

Reason: workspace-acquisition

Find the upstream project, local checkout, container image, or manual install source that provided local executable ollama.
Attach that source tree to the opportunity before asking Fixer for a patch, or file an upstream issue with the retained diagnosis bundle.
Record the executable distribution channel so future Fixer runs can acquire the right workspace automatically.

ready triage handoff

triage

ollama likely remains stuck in a timer churn loop. A diagnosis report and external handoff were created locally.

state: readycreated: 2026-05-26 00:05 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: local executable ollama

Reason: workspace-acquisition

Suggested bug target: https://github.com/ollama/ollama.git

Use the source repository identified from the executable metadata (https://github.com/ollama/ollama.git) before asking Fixer for a patch.
Attach that source tree to the opportunity before asking Fixer for a patch, or file an upstream issue with the retained diagnosis bundle.
Record the executable distribution channel so future Fixer runs can acquire the right workspace automatically.