ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through alloc_pages_noprof, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-19 01:27 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90573 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.
Full published attempt: /issues/019e3a1e-754b-7412-98c3-2dd07204d546. Issue JSON: /v1/issues/019e3a1e-754b-7412-98c3-2dd07204d546
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 ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-19 01:22 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90571 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.
Full published attempt: /issues/019e3db4-6e7f-7623-8a87-e638d5bbe8c6. Issue JSON: /v1/issues/019e3db4-6e7f-7623-8a87-e638d5bbe8c6
ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through entry_SYSRETQ_unsafe_stack, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-19 00:34 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90566 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.
Full published attempt: /issues/019db5d4-2ea0-7ce0-b14b-c1ab56004bc1. Issue JSON: /v1/issues/019db5d4-2ea0-7ce0-b14b-c1ab56004bc1
ollama is stuck in a likely timer churn loop: 33.33% of sampled CPU passed through exit_to_user_mode_loop, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-19 00:15 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90565 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.
Full published attempt: /issues/019e3b2e-7ef6-7b11-9c4c-6f384a55501d. Issue JSON: /v1/issues/019e3b2e-7ef6-7b11-9c4c-6f384a55501d
ollama is stuck in a likely unclassified userspace loop: 27.44% of sampled CPU passed through completion_done, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-19 00:09 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90564 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.
Full published attempt: /issues/019deff5-c840-7093-8f38-874efcc42398. Issue JSON: /v1/issues/019deff5-c840-7093-8f38-874efcc42398
ollama is stuck in a likely unclassified userspace loop: 50.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 0x000055c5c397a50e in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-19 00:03 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90562 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.
Full published attempt: /issues/019d3d61-d23a-7be3-8cd5-36c8732e0ae8. Issue JSON: /v1/issues/019d3d61-d23a-7be3-8cd5-36c8732e0ae8
ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through dequeue_entity, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-18 22:57 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90559 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.
Full published attempt: /issues/019d54c1-aea7-73d3-9307-abdff02e2f69. Issue JSON: /v1/issues/019d54c1-aea7-73d3-9307-abdff02e2f69
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through update_cfs_group, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-18 06:53 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e39a7-acec-7e33-a7c7-a6cc343e4456. Issue JSON: /v1/issues/019e39a7-acec-7e33-a7c7-a6cc343e4456
sshd-auth is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through cfree, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-18 03:43 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e381f-de92-7bc1-aa2f-447d68e2f337. Issue JSON: /v1/issues/019e381f-de92-7bc1-aa2f-447d68e2f337
ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through _raw_spin_trylock, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c397a50e in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-17 17:12 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90366 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.
Full published attempt: /issues/019ded48-a351-7db1-b2cd-e2a5a99f7943. Issue JSON: /v1/issues/019ded48-a351-7db1-b2cd-e2a5a99f7943
ollama is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through sched_balance_newidle, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-17 16:38 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90360 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.
Full published attempt: /issues/019df02b-72a4-7761-9397-e177a31b290a. Issue JSON: /v1/issues/019df02b-72a4-7761-9397-e177a31b290a
python3.11 is stuck in a likely busy poll loop: 25.66% of sampled CPU passed through fput, with repeated thread backtraces show 24 thread(s) around 0x00007fcc05248f16 in ?? () from target:<path>.
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-17 15:25 UTCvalidation: ready
Attempt Summary
python3.11 likely remains stuck in a busy-poll loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90358 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.
Full published attempt: /issues/019deedb-94f3-7283-b805-89912a5d531b. Issue JSON: /v1/issues/019deedb-94f3-7283-b805-89912a5d531b
ollama is stuck in a likely unclassified userspace 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 ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-17 15:17 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90355 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.
Full published attempt: /issues/019d3e52-af65-7fc0-8bde-cb0d66558df4. Issue JSON: /v1/issues/019d3e52-af65-7fc0-8bde-cb0d66558df4
ollama is stuck in a likely timer churn loop: 48.66% of sampled CPU passed through fput, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-16 02:26 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90353 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.
Full published attempt: /issues/019e1d17-4102-7990-9fc5-5b7e6c0f318e. Issue JSON: /v1/issues/019e1d17-4102-7990-9fc5-5b7e6c0f318e
ollama is stuck in a likely timer churn loop: 25.00% of sampled CPU passed through __pollwait, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 23:59 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90342 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.
Full published attempt: /issues/019d5a4d-2a99-7f50-8b1c-afedc974159d. Issue JSON: /v1/issues/019d5a4d-2a99-7f50-8b1c-afedc974159d
ollama is stuck in a likely unclassified userspace loop: 25.00% 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 ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 23:05 UTCvalidation: ready
Attempt Summary
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
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.
Full published attempt: /issues/019df910-cc70-7c62-addd-c380bd22f920. Issue JSON: /v1/issues/019df910-cc70-7c62-addd-c380bd22f920
ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through add_wait_queue, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 22:59 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90332 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.
Full published attempt: /issues/019d3ff7-aacb-70a1-8640-4c0488fd95b2. Issue JSON: /v1/issues/019d3ff7-aacb-70a1-8640-4c0488fd95b2
ollama is stuck in a likely timer churn loop: 25.00% of sampled CPU passed through __rseq_handle_notify_resume, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 22:41 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90330 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.
Full published attempt: /issues/019e2167-62bd-7611-a216-57737a2b1914. Issue JSON: /v1/issues/019e2167-62bd-7611-a216-57737a2b1914
ollama is stuck in a likely unclassified userspace 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 ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 22:36 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90327 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.
Full published attempt: /issues/019dd039-c241-7ee0-8262-e0cd451ba20e. Issue JSON: /v1/issues/019dd039-c241-7ee0-8262-e0cd451ba20e
ollama is stuck in a likely timer churn loop: 8.33% of sampled CPU passed through __percpu_counter_sum, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 21:24 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90317 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.
Full published attempt: /issues/019e21ef-2fb9-7443-9983-3565273d76a1. Issue JSON: /v1/issues/019e21ef-2fb9-7443-9983-3565273d76a1
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 ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 21:07 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90316 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.
Full published attempt: /issues/019dbcec-f056-7ae0-bc8f-d6d03bb07fcc. Issue JSON: /v1/issues/019dbcec-f056-7ae0-bc8f-d6d03bb07fcc
ollama is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through get_page_from_freelist, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 20:39 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90315 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.
Full published attempt: /issues/019dda03-7a8c-78a1-8b1d-a91b4d69aeb9. Issue JSON: /v1/issues/019dda03-7a8c-78a1-8b1d-a91b4d69aeb9
ollama is stuck in a likely unclassified userspace loop: 26.51% of sampled CPU passed through poll_schedule_timeout.constprop.0, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 20:24 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90312 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.
Full published attempt: /issues/019da24d-b4a2-70e3-8ce0-b0307efad6c4. Issue JSON: /v1/issues/019da24d-b4a2-70e3-8ce0-b0307efad6c4
ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through __get_user_8, with repeated thread backtraces show 1 thread(s) around 0x000055c5c397a50e in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 19:30 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90308 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.
Full published attempt: /issues/019da1fb-dcb3-72b1-ba41-1fd6b172a97c. Issue JSON: /v1/issues/019da1fb-dcb3-72b1-ba41-1fd6b172a97c
ollama is stuck in a likely timer churn loop: 33.33% of sampled CPU passed through timerqueue_add, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 19:16 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90306 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.
Full published attempt: /issues/019e2c8c-7197-7c42-bd9a-8d239b7918c0. Issue JSON: /v1/issues/019e2c8c-7197-7c42-bd9a-8d239b7918c0
ollama is stuck in a likely unclassified userspace loop: 20.00% of sampled CPU passed through __alloc_frozen_pages_noprof, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 19:11 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90305 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.
Full published attempt: /issues/019d62e0-f9a9-7d30-9b0f-5b0b64ab3425. Issue JSON: /v1/issues/019d62e0-f9a9-7d30-9b0f-5b0b64ab3425
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through nf_conntrack_tcp_packet, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-15 16:57 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e2c8c-71b2-7410-b0fd-4588b13c156a. Issue JSON: /v1/issues/019e2c8c-71b2-7410-b0fd-4588b13c156a
ollama is stuck in a likely unclassified userspace loop: 66.67% of sampled CPU passed through fput, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 16:51 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90293 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.
Full published attempt: /issues/019dbb1d-f3d1-79d0-be89-356d1cb05fde. Issue JSON: /v1/issues/019dbb1d-f3d1-79d0-be89-356d1cb05fde
ollama is stuck in a likely unclassified userspace loop: 25.67% of sampled CPU passed through __calc_delta.constprop.0, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 15:24 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90280 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.
Full published attempt: /issues/019d53db-2f85-7180-8892-4b8246719415. Issue JSON: /v1/issues/019d53db-2f85-7180-8892-4b8246719415
ollama is stuck in a likely timer churn loop: 33.33% of sampled CPU passed through __update_load_avg_cfs_rq, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 14:35 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90266 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.
Full published attempt: /issues/019e263f-66da-7ba1-ad74-458b8260e4a6. Issue JSON: /v1/issues/019e263f-66da-7ba1-ad74-458b8260e4a6
ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through __update_load_avg_cfs_rq, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 14:30 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90264 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.
Full published attempt: /issues/019d9fe6-e847-7503-a049-db64847538ea. Issue JSON: /v1/issues/019d9fe6-e847-7503-a049-db64847538ea
ollama is stuck in a likely timer churn loop: 33.33% of sampled CPU passed through __alloc_frozen_pages_noprof, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 14:24 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90262 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.
Full published attempt: /issues/019e28d6-4dcd-7fe3-9a41-ee13f6e241c2. Issue JSON: /v1/issues/019e28d6-4dcd-7fe3-9a41-ee13f6e241c2
ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through _raw_spin_lock, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 14:19 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90261 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.
Full published attempt: /issues/019d4e49-f141-7763-8c4c-177bd24bea3d. Issue JSON: /v1/issues/019d4e49-f141-7763-8c4c-177bd24bea3d
ollama is stuck in a likely timer churn loop: 33.33% of sampled CPU passed through _raw_spin_lock, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 14:14 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90259 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.
Full published attempt: /issues/019e29f6-ed15-70d3-b85c-75722f65e526. Issue JSON: /v1/issues/019e29f6-ed15-70d3-b85c-75722f65e526
ollama is stuck in a likely timer churn loop: 25.00% 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 ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 13:33 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90255 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.
Full published attempt: /issues/019dd4d2-521a-7bc2-8b35-4929317528f3. Issue JSON: /v1/issues/019dd4d2-521a-7bc2-8b35-4929317528f3
ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through __rcu_read_unlock, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 13:18 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90250 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.
Full published attempt: /issues/019d8cf5-37ee-7713-ab6f-aa0455b29b54. Issue JSON: /v1/issues/019d8cf5-37ee-7713-ab6f-aa0455b29b54
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through __check_object_size, with repeated no dominant syscall sample was captured.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-15 13:01 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e2b9e-99e4-72e2-8fb3-f281af406e18. Issue JSON: /v1/issues/019e2b9e-99e4-72e2-8fb3-f281af406e18
ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through __put_user_8, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 12:08 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90243 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.
Full published attempt: /issues/019e2266-2c03-7f31-bc99-caf97e5f99f8. Issue JSON: /v1/issues/019e2266-2c03-7f31-bc99-caf97e5f99f8
ollama is stuck in a likely unclassified userspace loop: 20.00% 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 ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 12:03 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90242 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.
Full published attempt: /issues/019d780b-a338-7841-9ba2-3bf6ad9294de. Issue JSON: /v1/issues/019d780b-a338-7841-9ba2-3bf6ad9294de
ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through post_alloc_hook, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-15 02:12 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90175 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.
Full published attempt: /issues/019e2909-2a06-77a0-93dc-2614132964f5. Issue JSON: /v1/issues/019e2909-2a06-77a0-93dc-2614132964f5
ollama is stuck in a likely timer churn loop: 25.00% of sampled CPU passed through dequeue_task, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c397a50e in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-14 22:23 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in a timer churn loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90169 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.
Full published attempt: /issues/019e2892-14d8-7923-bcb0-529784ecb0e3. Issue JSON: /v1/issues/019e2892-14d8-7923-bcb0-529784ecb0e3
ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through __update_load_avg_se, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-14 21:20 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90167 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.
Full published attempt: /issues/019db12c-6407-7881-964e-6788195ec743. Issue JSON: /v1/issues/019db12c-6407-7881-964e-6788195ec743
ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through __pollwait, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-14 21:15 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90162 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.
Full published attempt: /issues/019dd09e-61b4-7ed0-a93f-a3480ebc9b11. Issue JSON: /v1/issues/019dd09e-61b4-7ed0-a93f-a3480ebc9b11
sshd-auth is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through unresolved offset, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-14 20:42 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e280a-4492-7191-b9ec-076dfc0d450f. Issue JSON: /v1/issues/019e280a-4492-7191-b9ec-076dfc0d450f
perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f25577e97d2 in ?? () from target:<path>.
highpackage: perl-basesource: perlscore: 106reports: 2successful triagetriaged: 2026-05-14 19:28 UTCvalidation: ready
Attempt Summary
perl likely remains stuck in a busy-poll loop. A diagnosis report and external handoff were created locally.
Likely owner
perl
Reason: likely-external-root-cause
Suggested bug target: https://dev.perl.org/perl5/
Next steps
- Confirm the hotspot still points at perl with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map perl to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Published Session Excerpt
## Plan Pass
## Problem
Fixer sampled `/usr/bin/perl -wT /usr/sbin/munin-node --foreground` and labeled repeated `pselect6` as a likely busy poll. The embedded evidence instead shows the process sleeping in `pselect6` with ~0.55s and ~2.00s timeouts, `State: S`, `wchan: poll_schedule_timeout`, and only `0.1%` CPU. That is consistent with `munin-node`’s event loop waiting, not a demonstrated Perl interpreter runaway.
## Evidence Confidence
inferred
The trace was observed by Fixer, but the conclusion that Perl has a source bug is not supported. The application entrypoint is `munin-node`; Perl’s `pp_sselect` is only the runtime implementation of script-level `select`. The raw artifact paths named in `evidence.json` were not present locally, so I cannot independently inspect more than the embedded excerpts.
## Proposed Subject
No Perl source patch: reject/redirect the busy-poll finding for `munin-node` `select` wait
## Patch Plan
Do not edit Perl in this pass. Report this as a no-patch diagnosis unless extra evidence shows `select` returning immediately or Perl corrupting timeout/fd-set handling.
If later evidence proves a Perl runtime issue, investigate `pp_sys.c` `pp_sselect`, following the local conventions already present there: `PerlSock_select`, Perl SV APIs such as `SvGETMAGIC`/`SvPVX`, `SETERRNO` where appropriate, `Newx`/`Safefree` for allocations, and no avoidable `goto`. I found no relevant local helper for application-level event loops because `munin-node` is outside this source tree.
No prior Fixer patch was present in the workspace (`git status --short` was clean), so there is no previous patch to replace.
## Risks
Patching Perl based only on this profile would likely change correct `select` behavior and risk portability regressions across the platforms called out by `pod/perlhack.pod`.
The main uncertainty is missing raw artifacts; the plan should not claim a reproduced Perl bug without collecting a trace that shows rapid zero-timeout or immediate-return `select` calls under controlled conditions.
## Validation
Before any source-patch claim, try the project-level entrypoint from the workspace root:
`./Configure -des -Dusedevel && make -j2 && make test_harness`
If that fails because of missing dependencies or generated files, record the exact failure and then run the narrowest relevant test, likely `make test_harness TEST_FILES=t/op
[truncated]
Full published attempt: /issues/019dc07f-d19d-7cd0-8771-a7f51e5fec2b. Issue JSON: /v1/issues/019dc07f-d19d-7cd0-8771-a7f51e5fec2b
ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through do_syscall_64, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-14 19:13 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90150 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.
Full published attempt: /issues/019e26fa-6ba5-7af1-b67e-a6164b3294a8. Issue JSON: /v1/issues/019e26fa-6ba5-7af1-b67e-a6164b3294a8
ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through _raw_spin_unlock_irqrestore, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-14 19:08 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90149 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.
Full published attempt: /issues/019d81f7-e601-75f3-a77f-f63b774d35e0. Issue JSON: /v1/issues/019d81f7-e601-75f3-a77f-f63b774d35e0
ollama is stuck in a likely unclassified userspace loop: 33.33% of sampled CPU passed through policy_nodemask, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().
highsource: linuxscore: 106reports: 1successful triagetriaged: 2026-05-14 17:54 UTCvalidation: ready
Attempt Summary
ollama likely remains stuck in an unclassified userspace loop. A diagnosis report was created even though no patchable workspace was available: opportunity 90146 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.
Full published attempt: /issues/019e272d-7a5d-75f1-89f4-1d0dca2e39fe. Issue JSON: /v1/issues/019e272d-7a5d-75f1-89f4-1d0dca2e39fe
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 triagetriaged: 2026-05-14 17:48 UTCvalidation: ready
Attempt Summary
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.
Full published attempt: /issues/019e1868-943f-7523-b360-15bff15f0a65. Issue JSON: /v1/issues/019e1868-943f-7523-b360-15bff15f0a65
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through ip_finish_output2, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-14 13:47 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e2694-9a54-7071-86a7-632e6285f412. Issue JSON: /v1/issues/019e2694-9a54-7071-86a7-632e6285f412
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through unresolved offset, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-13 09:08 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e2078-d1a4-74b3-bda0-47898d09c470. Issue JSON: /v1/issues/019e2078-d1a4-74b3-bda0-47898d09c470
python3.13 is stuck in a likely unclassified userspace loop: 7.01% of sampled CPU passed through update_curr, with repeated sched_yield x306829, futex x5952, lseek x3156.
highpackage: python3.13-minimalsource: python3.13score: 106reports: 1successful triagetriaged: 2026-05-13 04:41 UTCvalidation: ready
Attempt Summary
python3.13 likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019df9be-9d3c-79a2-90da-27fbaa284532. Issue JSON: /v1/issues/019df9be-9d3c-79a2-90da-27fbaa284532
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through EVP_DigestUpdate, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-13 01:54 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e1aef-da36-7ee2-9139-a41a2bb22bdd. Issue JSON: /v1/issues/019e1aef-da36-7ee2-9139-a41a2bb22bdd
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through iommu_dma_alloc_iova, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-12 20:29 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e1b46-7d65-7ed2-a1b4-ac265fb7030e. Issue JSON: /v1/issues/019e1b46-7d65-7ed2-a1b4-ac265fb7030e
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through unresolved offset, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-10 21:03 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e0204-2523-7f73-8ec7-86c718857ae2. Issue JSON: /v1/issues/019e0204-2523-7f73-8ec7-86c718857ae2
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through tcp_rearm_rto, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-10 20:19 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e03a2-987c-7081-9f35-21414b0a6e32. Issue JSON: /v1/issues/019e03a2-987c-7081-9f35-21414b0a6e32
python3.13 is stuck in a likely busy poll loop: 20.18% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 2 thread(s) around 0x00007fa97251bffe in ?? () from target:<path> and 1 thread(s) around 0x00007fa970081594 in ?? () from target:<path>.
highpackage: python3.13-minimalsource: python3.13score: 106reports: 2successful triagetriaged: 2026-05-10 19:56 UTCvalidation: ready
Attempt Summary
python3.13 likely remains stuck in a busy-poll loop. A diagnosis report and external handoff were created locally.
Likely owner
python3.13
Reason: likely-external-root-cause
Next steps
- Confirm the hotspot still points at python3.13 with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map python3.13 to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Published Session Excerpt
## Plan Pass
## Problem
Fixer observed high CPU in `/usr/bin/python3.13` while running `/usr/bin/python3 /usr/bin/unattended-upgrade`, but the evidence does not identify a CPython runtime loop. The hot path is `apt_pkg.cpython-313-x86_64-linux-gnu.so`, with additional samples in `libapt-pkg.so.7.0.0`, and strace shows repeated `newfstatat()` probes under `/var/lib/apt/lists`.
## Evidence Confidence
inferred
## Proposed Subject
No CPython patch in this pass. Diagnose as likely misattributed to `python3.13`; the actionable target appears to be `python3-apt`, `libapt-pkg`, or `unattended-upgrades`.
## Patch Plan
1. Do not edit CPython unless a bounded reproduction shows CPython itself issuing the repeated path stats or causing an extension-level busy loop.
2. Treat `/usr/bin/unattended-upgrade` as the first investigation target, per the evidence command line, and inspect `python3-apt`/APT cache behavior before CPython runtime code.
3. If later evidence does identify a CPython caller, follow CPython conventions from `README.rst` and subsystem helpers such as `_Py_stat()`, `_Py_fstat()`, `_Py_wstat()`, `PyMem_Raw*`, and existing path/file utility wrappers rather than direct generic libc calls.
4. Avoid awkward control flow such as adding `goto` cleanup where a bounded early-return or existing helper pattern is cleaner.
5. No prior Fixer patch was found in this workspace to improve or replace.
## Risks
A CPython patch based only on this evidence would likely be speculative and upstream-hostile: the sampled Python frames show interpreter dispatch into an extension, while the hot DSO and syscall pattern point outside this source package. Patching CPython could mask the report without addressing the APT cache/stat behavior that Fixer observed.
## Validation
Before any future source edit, try the project entrypoint from the workspace root: `./configure && make`. If it fails because Debian source build dependencies or generated files are missing, record the exact failing command and error.
For the independent failure-signal check, run a bounded local probe such as `timeout 10s strace -f -e newfstatat /usr/bin/python3 /usr/bin/unattended-upgrade --dry-run` only if safe in the test environment, and verify whether repeated `/var/lib/apt/lists/*` stats occur. If not safe, use a narrower Python import/cache smoke check around `apt_pkg`/APT cache construction rather t
[truncated]
Full published attempt: /issues/019dd98b-0e1d-76e3-9171-f0f72c689536. Issue JSON: /v1/issues/019dd98b-0e1d-76e3-9171-f0f72c689536
sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through __nf_conntrack_find_get, with repeated restart_syscall x1.
highpackage: openssh-serversource: opensshscore: 106reports: 1successful triagetriaged: 2026-05-10 18:41 UTCvalidation: ready
Attempt Summary
sshd-auth likely remains stuck in an unclassified userspace loop. Fixer produced a diagnosis report and intentionally skipped an automatic package patch attempt because the evidence is not specific enough to choose a safe source change.
Likely owner
external dependency or workload outside the current source tree
Reason: weak-unknown-runaway-evidence
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019e1087-6b5c-7fa1-9038-a21ad4e3543e. Issue JSON: /v1/issues/019e1087-6b5c-7fa1-9038-a21ad4e3543e
postgres is stuck in a likely file not found retry loop: 24.27% of sampled CPU passed through verify_compact_attribute, with repeated pread64 x5175, unlink x438, close x96.
highpackage: postgresql-18source: postgresql-18score: 106reports: 2successful triagetriaged: 2026-04-30 22:12 UTCvalidation: ready
Attempt Summary
postgres likely remains stuck in a file-not-found retry loop. A diagnosis report was created even though no patchable workspace was available: could not acquire a workspace for external package postgresql-18; no Debian source package, Debian VCS metadata, or cloneable upstream repository is available
Likely owner
postgresql-18
Reason: workspace-acquisition
Suggested bug target: http://www.postgresql.org/
Next steps
- File an upstream or vendor issue with the diagnosis bundle and package metadata.
- Include the workspace acquisition note so maintainers know why no local source patch was attempted.
Full published attempt: /issues/019dd481-79fe-76a1-9836-649c2f43b707. Issue JSON: /v1/issues/019dd481-79fe-76a1-9836-649c2f43b707
element-desktop was killed by the kernel OOM killer after reaching about 200 MiB anonymous RSS in `element-desktop`.
highsource: element-desktopscore: 108reports: 2successful triagetriaged: 2026-03-30 16:40 UTCvalidation: ready
Attempt Summary
element-desktop was killed by the kernel OOM killer. Fixer produced a diagnosis report and intentionally skipped a package patch attempt because the wait appears to be below user space.
Likely owner
external dependency or workload outside the current source tree
Reason: likely-external-root-cause
Next steps
- Confirm the hotspot still points at external dependency or workload outside the current source tree with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map external dependency or workload outside the current source tree to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019d3b87-bd34-7ee0-b96a-5db52867a542. Issue JSON: /v1/issues/019d3b87-bd34-7ee0-b96a-5db52867a542
postgres is stuck in a likely busy poll loop: 22.73% of sampled CPU passed through [.] 0x000000000001066e, with repeated epoll_wait x1.
highpackage: postgresql-18source: postgresql-18score: 106reports: 2successful triagetriaged: 2026-03-29 16:36 UTCvalidation: ready
Attempt Summary
postgres likely remains stuck in a busy poll loop. A diagnosis report and external handoff were created locally.
Likely owner
module `h3_postgis.so` or the workload driving it
Reason: likely-external-root-cause
Next steps
- Confirm the hotspot still points at module `h3_postgis.so` or the workload driving it with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map module `h3_postgis.so` or the workload driving it to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Published Session Excerpt
**Root Cause**
The evidence does not support a PostgreSQL core busy-poll bug in the sampled process.
`/proc` shows the sampled `postgres` process sleeping in `ep_poll`, with kernel stack `ep_poll -> do_epoll_wait`, and `strace` shows long `epoll_wait(..., 60000)` calls being interrupted only by `SIGCHLD` and new accepts. That matches normal postmaster behavior, not a spin loop. The CPU hotspot from perf was instead in a deleted external module, `h3_postgis.so`, which is not present anywhere in this source tree. The child backends visible in `strace` are executing short-lived application queries and loading external extensions like `vector.so`; nothing in the captured trace points to a tight loop in PostgreSQL’s wait/latch code in [pqcomm.c](./workspace/src/backend/libpq/pqcomm.c), [latch.c](./workspace/src/backend/storage/ipc/latch.c), or [waiteventset.c](./workspace/src/backend/storage/ipc/waiteventset.c).
The most likely root cause is CPU burn inside an extension/query workload in backend children, with the investigation bundle attributing it to the wrong `postgres` process. The strongest lead is the external `h3_postgis.so` mapping from perf, not PostgreSQL core.
**Patch**
No source change landed. A core PostgreSQL patch here would be speculative and unsafe because the implicated code is outside this repository.
**Validation**
I validated this by:
- Reading the evidence bundle and the actual investigation artifacts on disk.
- Confirming the sampled process was blocked in `epoll_wait`, not runnable in a userspace spin.
- Searching the repository and Debian packaging: there is no `h3_postgis`/PostGIS code in this source tree.
- Reviewing the relevant wait-path implementation in core PostgreSQL; nothing in the captured behavior contradicts normal operation.
No tests were run because no safe code change was made.
For an upstream report, the actionable target is the `h3_postgis`/extension stack or the application query workload, with the key points:
- perf hotspot in deleted `h3_postgis.so`
- sampled postmaster actually sleeping in `epoll_wait`
- repeated short-lived backend children handling application SQL
- repository under test does not contain the implicated extension code
Full published attempt: /issues/019d3a3b-0e57-7393-a88a-5ddf422b5e86. Issue JSON: /v1/issues/019d3a3b-0e57-7393-a88a-5ddf422b5e86
Top frame: n/a [libEGL_nvidia.so.0]
highpackage: google-chrome-stablesource: google-chrome-stablescore: 98reports: 1successful triagetriaged: 2026-03-29 14:36 UTCvalidation: ready
Attempt Summary
A diagnosis and external handoff were created locally because Fixer could not acquire a patchable workspace for google-chrome-stable.
Likely owner
google-chrome-stable
Reason: workspace-acquisition
Next steps
- Confirm the hotspot still points at google-chrome-stable with a fresh perf sample before filing the bug.
- Capture the actual hot backend or child process rather than the parent service wrapper if the issue recurs.
- Map google-chrome-stable to its owning package or project and file an upstream or distro bug with the summarized evidence.
- If the owner is still unclear, collect another short strace plus `/proc/<pid>/maps` at the moment of the spike.
Full published attempt: /issues/019d39bb-3671-7203-9ebb-706e5ee6e351. Issue JSON: /v1/issues/019d39bb-3671-7203-9ebb-706e5ee6e351