Public issue detail

Runaway CPU investigation for ollama: unknown userspace loop at clockevents_program_event

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

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

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 x52, epoll_pwait x1, restart_syscall 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 _nv041602rm

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 8.18% of sampled CPU passed through _nv041602rm, 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 15:00 UTC. Public page: /issues/019d962c-a2c3-7fb2-b09e-d9d9a2c5de67. Public JSON: /v1/issues/019d962c-a2c3-7fb2-b09e-d9d9a2c5de67

Runaway CPU investigation for ollama: unknown userspace loop at __free_frozen_pages

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through __free_frozen_pages, 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 14:04 UTC. Public page: /issues/019ddcf8-c6f9-7af1-b369-6aaa444bcac3. Public JSON: /v1/issues/019ddcf8-c6f9-7af1-b369-6aaa444bcac3

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 classification, 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: unknown userspace loop at _copy_from_user

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through _copy_from_user, 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 00:32 UTC. Public page: /issues/019d7866-5dd9-7390-b7d6-7380b0b8c408. Public JSON: /v1/issues/019d7866-5dd9-7390-b7d6-7380b0b8c408

Runaway CPU investigation for ollama: unknown userspace loop at avg_vruntime

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through avg_vruntime, 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-05 17:35 UTC. Public page: /issues/019e6621-6981-7373-bc3f-c9bda665a390. Public JSON: /v1/issues/019e6621-6981-7373-bc3f-c9bda665a390

Runaway CPU investigation for ollama: unknown userspace loop at __rmqueue_pcplist

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through __rmqueue_pcplist, 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-05 13:52 UTC. Public page: /issues/019d52e7-0e89-7b52-a766-d41ecb043bde. Public JSON: /v1/issues/019d52e7-0e89-7b52-a766-d41ecb043bde

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.