Public issue detail

Runaway CPU investigation for ollama: unknown userspace loop at clear_page_erms

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

highsource: linuxscore: 106reports: 1successful triage

Last seen: 2026-05-16 05:51 UTC. Public JSON: /v1/issues/019e1868-943f-7523-b360-15bff15f0a65

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-14 17:48 UTCvalidation: ready

ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90145 has no repo root, package name, or source package

Likely owner

the upstream maintainer

Reason: workspace-acquisition

Next steps

Review the package metadata and attach a source tree or upstream clone if one exists.
If no patchable tree is available, file an external bug using the diagnosis bundle.

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: 14.08% 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: 2similarity: 99%

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

Last seen: 2026-05-16 01:30 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 entry_SYSCALL_64_after_hwframe

possible duplicate

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