Public issue detail

Runaway CPU investigation for ollama: unknown userspace loop at dequeue_entities

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

highscore: 106reports: 1successful triage

Last seen: 2026-06-05 09:07 UTC. Public JSON: /v1/issues/019df910-cc70-7c62-addd-c380bd22f920

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-15 23:05 UTCvalidation: ready

ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90335 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: The process is demonstrably CPU-hot, but the current syscall and symbol sample does not point to a single dominant loop family yet.
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: unknown userspace loop at unresolved offset in ollama

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 12.27% 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: 3successful triagesimilarity: 99%

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

Last seen: 2026-06-10 04:46 UTC. Public page: /issues/019dd7a7-430c-79a0-bc5b-7549a044b3fc. Public JSON: /v1/issues/019dd7a7-430c-79a0-bc5b-7549a044b3fc

Runaway CPU investigation for ollama: unknown userspace loop at clockevents_program_event

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through clockevents_program_event, 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

Last seen: 2026-06-09 10:40 UTC. Public page: /issues/019dd8d5-aace-7b80-b142-66a042562330. Public JSON: /v1/issues/019dd8d5-aace-7b80-b142-66a042562330

Runaway CPU investigation for ollama: unknown userspace loop at _raw_spin_lock_irqsave

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 27.48% 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-06 23:28 UTC. Public page: /issues/019d780b-a338-7841-9ba2-3bf6ad9294de. Public JSON: /v1/issues/019d780b-a338-7841-9ba2-3bf6ad9294de

Runaway CPU investigation for ollama: unknown userspace loop at __list_del_entry_valid_or_report

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through __list_del_entry_valid_or_report, 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

Last seen: 2026-06-06 22:01 UTC. Public page: /issues/019d3d61-d23a-7be3-8cd5-36c8732e0ae8. Public JSON: /v1/issues/019d3d61-d23a-7be3-8cd5-36c8732e0ae8

Runaway CPU investigation for ollama: unknown userspace loop at unmap_page_range

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 19.75% of sampled CPU passed through unmap_page_range, 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-06 19:51 UTC. Public page: /issues/019dd3df-b6d5-7c33-9312-fed3ac8a5dbe. Public JSON: /v1/issues/019dd3df-b6d5-7c33-9312-fed3ac8a5dbe

Runaway CPU investigation for ollama: unknown userspace loop at psi_task_switch

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through psi_task_switch, 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 18:37 UTC. Public page: /issues/019e4578-9b71-7c82-b7f1-5bfe5a37cc8e. Public JSON: /v1/issues/019e4578-9b71-7c82-b7f1-5bfe5a37cc8e

Worker outcome summary

This issue has 1 recorded worker attempt. 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.

1 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 (1 attempt)

Published attempts

ready triage handoff

triage

state: readycreated: 2026-05-15 23: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.