Problems people are most likely to feel first

Repeated EGL/Mesa/Qt desktop warnings affected kwin_wayland, plasmashell, org_kde_powerdevil, xdg-desktop-portal-kde, org.kde.kwalletd6 on KDE Wayland desktop, suggesting a shared compositor or graphics-session failure.

Likely user impact. The desktop graphics session likely felt broadly broken: multiple apps may have failed to launch, windows may have stopped painting correctly, or the session may have become unstable.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:02 UTC. Details · JSON

After suspend/resume, radeon X11 desktop failed: Xorg crashed after GPU/display errors, and sddm restarted the display stack.

Likely user impact. After wake-from-sleep, the desktop likely came back blank, broken, or dropped the user back to login.

Cluster size: single-host issue family. Last seen 2026-07-06 15:53 UTC. Details · JSON

After suspend/resume, nouveau X11 desktop failed: Xorg crashed after GPU/display errors, and sddm restarted the display stack.

Likely user impact. After wake-from-sleep, the desktop likely came back blank, broken, or dropped the user back to login.

Cluster size: single-host issue family. Last seen 2026-07-06 15:53 UTC. Details · JSON

Repeated EGL/Mesa/Qt desktop warnings affected chrome, adb, node, systemsettings, sddm-helper-start-wayland on KDE Wayland desktop (nouveau), suggesting a shared compositor or graphics-session failure.

Likely user impact. The desktop graphics session likely felt broadly broken: multiple apps may have failed to launch, windows may have stopped painting correctly, or the session may have become unstable.

Cluster size: single-host issue family. Last seen 2026-05-27 05:28 UTC. Details · JSON

Repeated EGL/Mesa/Qt desktop warnings affected Xorg on desktop desktop desktop (radeon), suggesting a shared compositor or graphics-session failure.

Likely user impact. The desktop graphics session likely felt broadly broken: multiple apps may have failed to launch, windows may have stopped painting correctly, or the session may have become unstable.

Cluster size: single-host issue family. Last seen 2026-07-06 15:53 UTC. Details · JSON

element-desktop was killed by the kernel OOM killer after reaching about 200 MiB anonymous RSS in `element-desktop`.

Likely user impact. The system likely ran out of memory and killed element-desktop, so work in that app or task may have vanished.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:02 UTC. Details · JSON

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through Perl_runops_standard, with repeated pselect6 x4.

Likely user impact. perl likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 3-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 6.41% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007fdd05c9b72e in ?? () and 1 thread(s) around 0x00007fdd05c9b72e in ?? ().

Likely user impact. a Python workload likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 3-host issue family. Last seen 2026-07-09 19:56 UTC. Details · JSON

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 ?? ().

Likely user impact. ollama likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 3-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

python was killed by the kernel OOM killer after reaching about 11717 MiB anonymous RSS in `org.kde.yakuake`.

Likely user impact. The system likely ran out of memory and killed a Python workload, so work in that app or task may have vanished.

Cluster size: single-host issue family. Last seen 2026-03-31 12:57 UTC. Details · JSON

chrome was killed by the kernel OOM killer after reaching about 6520 MiB anonymous RSS in `google-chrome`.

Likely user impact. The system likely ran out of memory and killed chrome, so work in that app or task may have vanished.

Cluster size: single-host issue family. Last seen 2026-03-30 21:50 UTC. Details · JSON

slack was killed by the kernel OOM killer after reaching about 334 MiB anonymous RSS in `slack`.

Likely user impact. The system likely ran out of memory and killed slack, so work in that app or task may have vanished.

Cluster size: single-host issue family. Last seen 2026-03-30 19:49 UTC. Details · JSON

postgres shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via an unknown wait point.

Likely user impact. PostgreSQL likely looked hung or stopped making progress.

Cluster size: 3-host issue family. Last seen 2026-05-27 05:34 UTC. Details · JSON

sshd-auth is stuck in a likely timer churn loop: 100.00% of sampled CPU passed through apparmor_socket_recvmsg, with repeated thread backtraces show 1 thread(s) around 0x00007fa460a9a7d2 in ?? () from target:<path>.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

sshd-auth is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through unresolved offset, with repeated read x3, write x2, clock_nanosleep x1.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

sshd-auth is stuck in a likely timer churn loop: 100.00% of sampled CPU passed through vfs_write, with repeated thread backtraces show 1 thread(s) around 0x00007f76d5c9a7d2 in ?? () from target:<path>.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

smtpd is stuck in a likely unclassified userspace loop: 21.02% of sampled CPU passed through __memcg_slab_post_alloc_hook, with repeated thread backtraces show 1 thread(s) around 0x00007f059d1bc7d2 in ?? () from target:<path>.

Likely user impact. smtpd likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

dockerd is stuck in a likely socket churn loop: 100.00% of sampled CPU passed through bpf_lsm_file_permission, with repeated thread backtraces show 1 thread(s) around 0x000056124fea7023 in ?? () and 1 thread(s) around 0x000056124fea7023 in ?? ().

Likely user impact. dockerd likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 9.10% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007fbc72ca5ffe in ?? () and 1 thread(s) around 0x00007fbc72ca5ffe in ?? ().

Likely user impact. redis-check-rdb likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

python3.13 is stuck in a likely file not found retry loop: 9.65% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 2 thread(s) around 0x00007f6145cf24be in ?? () from target:<path> and 1 thread(s) around 0x00007f614384e594 in ?? () from target:<path>.

Likely user impact. a Python workload likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:11 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 6.51% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f89688a74be in ?? () and 1 thread(s) around 0x00007f89688a74be in ?? ().

Likely user impact. redis-check-rdb likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-09 13:37 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through _PyEval_EvalFrameDefault, with repeated thread backtraces show 1 thread(s) around 0x00007f091ce537d2 in ?? () from target:<path>.

Likely user impact. a Python workload likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-02 23:40 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through sock_poll, with repeated thread backtraces show 1 thread(s) around 0x00007f35fa09a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-27 17:58 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 5.26% of sampled CPU passed through num_to_str, with repeated thread backtraces show 1 thread(s) around 0x00007fbc72ca5ffe in ?? () and 1 thread(s) around 0x00007fbc72ca5ffe in ?? ().

Likely user impact. redis-check-rdb likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 20:59 UTC. Details · JSON

sshd-auth is stuck in a likely timer churn loop: 50.00% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f51e0e9a7d2 in ?? () from target:<path>.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-23 20:24 UTC. Details · JSON

rsync is stuck in a likely busy poll loop: 24.28% of sampled CPU passed through clear_page_erms, with repeated thread backtraces show 1 thread(s) around 0x00007f1f5169a7d2 in ?? () from target:<path>.

Likely user impact. rsync likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-02 23:40 UTC. Details · JSON

python3.13 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 0x00007f091ce537d2 in ?? () from target:<path>.

Likely user impact. a Python workload likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-02 03:18 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 13.50% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f35fa09a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-27 21:56 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 9.30% of sampled CPU passed through mas_walk, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-27 00:10 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.35% of sampled CPU passed through try_charge_memcg, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-26 22:01 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 17.74% of sampled CPU passed through __vma_start_write, with repeated thread backtraces show 1 thread(s) around 0x00007f0dbde9a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-26 19:13 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.33% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-26 16:01 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 8.61% of sampled CPU passed through mas_store_gfp, with repeated thread backtraces show 1 thread(s) around 0x00007eff0e09a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-26 06:01 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.17% of sampled CPU passed through xas_load, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 20:22 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 10.22% of sampled CPU passed through clear_page_erms, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 15:06 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 7.17% of sampled CPU passed through hash_search_with_hash_value, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 13:52 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 16.80% of sampled CPU passed through memset_orig, with repeated thread backtraces show 1 thread(s) around 0x00007eff0e09a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 05:40 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 4.39% of sampled CPU passed through migrate_enable, with repeated thread backtraces show 1 thread(s) around 0x00007fbc72ca5ffe in ?? () and 1 thread(s) around 0x00007fbc72ca5ffe in ?? ().

Likely user impact. redis-check-rdb likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 03:29 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.56% of sampled CPU passed through lock_vma_under_rcu, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 01:00 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 6.89% of sampled CPU passed through __mem_cgroup_charge, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-24 23:46 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 10.75% of sampled CPU passed through __list_del_entry_valid_or_report, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-23 10:03 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 8.90% of sampled CPU passed through __memcg_slab_free_hook, with repeated thread backtraces show 1 thread(s) around 0x00007f9041a9a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-23 04:10 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 6.91% of sampled CPU passed through sync_regs, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-22 20:44 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 7.61% of sampled CPU passed through next_uptodate_folio, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-22 19:29 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 10.84% of sampled CPU passed through rtnl_dump_all, with repeated thread backtraces show 1 thread(s) around 0x00007efcc509a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-21 00:10 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 17.88% of sampled CPU passed through _copy_from_user, with repeated thread backtraces show 1 thread(s) around 0x00007efcc509a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-20 08:41 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 8.04% of sampled CPU passed through copy_mc_enhanced_fast_string, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-19 22:52 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through kfree, with repeated thread backtraces show 1 thread(s) around 0x00007efcc509a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-17 16:57 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 9.55% of sampled CPU passed through set_pte_range, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-17 16:20 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 20.12% of sampled CPU passed through kmem_cache_free, with repeated thread backtraces show 1 thread(s) around 0x00007f3f9ca9a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-16 21:06 UTC. Details · JSON

htop is stuck in a likely unclassified userspace loop: 10.31% of sampled CPU passed through lock_next_vma, with repeated no dominant syscall sample was captured.

Likely user impact. htop likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

packagekitd is stuck in a likely busy poll loop: 24.42% of sampled CPU passed through syscall_return_via_sysret, with repeated ppoll x4, futex x1.

Likely user impact. packagekitd likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:16 UTC. Details · JSON

systemd-userwork is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through native_queued_spin_lock_slowpath, with repeated prctl x4, capget x2, accept4 x1.

Likely user impact. systemd-userwork likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:02 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 15.28% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 2 thread(s) around 0x00007f35495474be in ?? () from target:<path> and 1 thread(s) around 0x000000000057151f in _PyEval_EvalFrameDefault ().

Likely user impact. a Python workload likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-07 10:15 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 13.49% of sampled CPU passed through copy_mc_enhanced_fast_string, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-27 04:49 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 20.28% of sampled CPU passed through next_uptodate_folio, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-27 02:02 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 11.40% of sampled CPU passed through native_irq_return_iret, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-26 18:54 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 11.93% of sampled CPU passed through filemap_map_pages, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-26 14:28 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 6.62% of sampled CPU passed through clear_page_erms, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-26 09:50 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 9.32% of sampled CPU passed through __handle_mm_fault, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-26 04:07 UTC. Details · JSON

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 0x00007fa21036a7d2 in ?? () from target:<path>.

Likely user impact. perl likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 20:59 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 10.84% of sampled CPU passed through folio_add_file_rmap_ptes, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 16:02 UTC. Details · JSON

ollama is stuck in a likely unclassified userspace loop: 12.32% 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 ?? ().

Likely user impact. ollama likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-07 10:52 UTC. Details · JSON

ollama is stuck in a likely timer churn loop: 48.28% of sampled CPU passed through fdget, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

Likely user impact. ollama likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-03 18:33 UTC. Details · JSON

ollama is stuck in a likely timer churn loop: 6.01% 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 ?? ().

Likely user impact. ollama likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-07-03 09:11 UTC. Details · JSON

ollama is stuck in a likely busy poll loop: 33.33% of sampled CPU passed through __rcu_read_lock, with repeated thread backtraces show 2 thread(s) around 0x00007f46f5d81ffe in ?? () from target:<path> and 1 thread(s) around 0x0000563a0acb7143 in ?? ().

Likely user impact. ollama likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-26 02:14 UTC. Details · JSON

ollama is stuck in a likely busy poll loop: 25.00% of sampled CPU passed through __rseq_handle_notify_resume, with repeated thread backtraces show 2 thread(s) around 0x00007f96534a5ffe in ?? () from target:<path> and 1 thread(s) around 0x0000564fcda6b143 in ?? ().

Likely user impact. ollama likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-25 23:28 UTC. Details · JSON

ollama is stuck in a likely busy poll loop: 22.14% of sampled CPU passed through _raw_spin_lock, with repeated thread backtraces show 2 thread(s) around 0x00007fa0dc0a5ffe in ?? () from target:<path> and 1 thread(s) around 0x0000560226725143 in ?? ().

Likely user impact. ollama likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: 2-host issue family. Last seen 2026-06-23 06:02 UTC. Details · JSON

python3.13 shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via folio_wait_bit_common.

Likely user impact. a Python workload likely looked hung or stopped making progress.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:02 UTC. Details · JSON

chrome shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via folio_wait_bit_common.

Likely user impact. chrome likely looked hung or stopped making progress.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:02 UTC. Details · JSON

upowerd shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via poll_schedule_timeout.constprop.0.

Likely user impact. upowerd likely looked hung or stopped making progress.

Cluster size: 2-host issue family. Last seen 2026-05-27 05:34 UTC. Details · JSON

systemd-journald shows a repeated `D`-state wait, likely blocked in unknown uninterruptible wait via do_epoll_wait.

Likely user impact. systemd-journald likely looked hung or stopped making progress.

Cluster size: 2-host issue family. Last seen 2026-05-27 05:34 UTC. Details · JSON

systemd shows a repeated `D`-state wait, likely blocked in nfs wait via __wait_rcu_gp.

Likely user impact. systemd likely looked hung or stopped making progress.

Cluster size: 2-host issue family. Last seen 2026-07-10 01:11 UTC. Details · JSON

htop is stuck in a likely file not found retry loop: 6.32% of sampled CPU passed through memset_orig, with repeated thread backtraces show 1 thread(s) around 0x00007f00ad0aecb2 in ?? () from target:<path>.

Likely user impact. htop likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-10 01:11 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 5.80% of sampled CPU passed through pthread_mutex_trylock, with repeated thread backtraces show 1 thread(s) around 0x00007f89688a74be in sem_trywait () and 1 thread(s) around 0x00007f89688a74be in sem_trywait ().

Likely user impact. redis-check-rdb likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-10 01:11 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 7.02% of sampled CPU passed through _dl_mcount_wrapper, with repeated thread backtraces show 1 thread(s) around 0x00007f89688a74be in sem_trywait () and 1 thread(s) around 0x00007f89688a74be in sem_trywait ().

Likely user impact. redis-check-rdb likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-09 22:57 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through do_fault, with repeated thread backtraces show 1 thread(s) around 0x00007f33aba9a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-08 12:09 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 24.67% of sampled CPU passed through __mod_node_page_state, with repeated thread backtraces show 1 thread(s) around 0x00007f57f0c9a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-08 12:09 UTC. Details · JSON

sshd-auth is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through rb_erase, with repeated read x3, write x2, clock_nanosleep x1.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-08 12:09 UTC. Details · JSON

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through native_sched_clock, with repeated thread backtraces show 1 thread(s) around 0x00007f5e185decb2 in ?? () from target:<path>.

Likely user impact. perl likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-07 21:30 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 4.80% of sampled CPU passed through update_curr, with repeated thread backtraces show 1 thread(s) around 0x00007f89688a74be in ?? () and 1 thread(s) around 0x00007f89688a74be in ?? ().

Likely user impact. redis-check-rdb likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-07 12:41 UTC. Details · JSON

python3.13 is stuck in a likely dbus spin loop: 3.95% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 2 thread(s) around 0x00007f2de17b84be in ?? () from target:<path> and 1 thread(s) around 0x00007f2de17b84be in ?? () from target:<path>.

Likely user impact. a Python workload likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-06 13:45 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 7.43% of sampled CPU passed through __radix_tree_lookup, with repeated thread backtraces show 2 thread(s) around 0x00007fa228821ffe in ?? () from target:<path> and 1 thread(s) around 0x00007fa228821ffe in ?? () from target:<path>.

Likely user impact. a Python workload likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-05 13:59 UTC. Details · JSON

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through update_sd_lb_stats.constprop.0, with repeated thread backtraces show 1 thread(s) around 0x00007f9a01ce47d2 in ?? () from target:<path>.

Likely user impact. perl likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-04 21:40 UTC. Details · JSON

smtpd is stuck in a likely busy poll loop: 14.11% of sampled CPU passed through unix_maybe_add_creds, with repeated thread backtraces show 1 thread(s) around 0x00007f529799e7d2 in ?? () from target:<path>.

Likely user impact. smtpd likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-04 06:14 UTC. Details · JSON

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through Perl_hv_iternext_flags, with repeated thread backtraces show 1 thread(s) around 0x00007f421c5d77d2 in ?? () from target:<path>.

Likely user impact. perl likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-04 05:55 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 9.89% of sampled CPU passed through memset_orig, with repeated thread backtraces show 2 thread(s) around 0x00007fa228821ffe in ?? () from target:<path> and 1 thread(s) around 0x00007fa225d50890 in QuoteString(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*) () from target:<path>.

Likely user impact. a Python workload likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-04 05:55 UTC. Details · JSON

sshd-auth is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through schedule_timeout, with repeated restart_syscall x1.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-02 22:27 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 28.29% of sampled CPU passed through uncharge_folio, with repeated thread backtraces show 1 thread(s) around 0x00007f57f0c9a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-02 22:27 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 10.87% of sampled CPU passed through audit_value_needs_encoding@plt, with repeated thread backtraces show 1 thread(s) around 0x00007faaa249a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-02 03:18 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 12.29% of sampled CPU passed through getuid@plt, with repeated thread backtraces show 1 thread(s) around 0x00007f4a7a09a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-07-01 21:48 UTC. Details · JSON

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through do_select, with repeated thread backtraces show 1 thread(s) around 0x00007f4392f987d2 in ?? () from target:<path>.

Likely user impact. perl likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-06-28 21:10 UTC. Details · JSON

sshd-auth is stuck in a likely timer churn loop: 50.00% of sampled CPU passed through read_tsc, with repeated read x3, write x2, clock_nanosleep x1.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-06-28 11:24 UTC. Details · JSON

sshd-auth is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through fdget_pos, with repeated no dominant syscall sample was captured.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-06-27 21:56 UTC. Details · JSON

sshd-auth is stuck in a likely unclassified userspace loop: 59.36% of sampled CPU passed through __free_one_page, with repeated restart_syscall x1.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-06-27 18:17 UTC. Details · JSON

redis-check-rdb is stuck in a likely dbus spin loop: 7.11% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007fbc72ca5ffe in ?? () and 1 thread(s) around 0x00007fbc72ca5ffe in ?? ().

Likely user impact. redis-check-rdb likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-06-27 16:08 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 21.85% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f0dbde9a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-06-27 08:47 UTC. Details · JSON

sshd-auth is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through pfn_to_dma_pte, with repeated restart_syscall x1.

Likely user impact. sshd-auth likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-06-26 19:13 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through __legitimize_mnt, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

Likely user impact. PostgreSQL likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-06-26 02:14 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 9.87% of sampled CPU passed through copy_page_range, with repeated thread backtraces show 1 thread(s) around 0x00007eff0e09a7d2 in ?? () from target:<path>.

Likely user impact. sshd-session likely made the app or machine feel hot, loud, or sluggish by burning CPU continuously.

Cluster size: single-host issue family. Last seen 2026-06-25 18:30 UTC. Details · JSON