Problems people are most likely to feel first

Repeated EGL/Mesa/Qt desktop warnings affected plasmashell, org_kde_powerdevil, xdg-desktop-portal-kde, DiscoverNotifier, google-chrome-stable 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-05-19 02:26 UTC. Details · JSON

After suspend/resume, radeon X11 desktop failed: Xorg, kwin_x11 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-05-19 02:35 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-05-19 02:35 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-19 02:35 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-05-19 02:35 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-04-03 22:55 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-05-19 02:26 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () 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: 3-host issue family. Last seen 2026-05-11 17:11 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

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-05-19 02:26 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-05-19 02:21 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-05-19 02:21 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 18.73% of sampled CPU passed through memset_orig, with repeated thread backtraces show 1 thread(s) around 0x00007f4c71e9a7d2 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-05-19 02:21 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.16% of sampled CPU passed through lru_gen_add_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-05-19 02:21 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 5.07% 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-05-19 02:21 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-05-19 02:02 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 4.24% 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-05-19 02:02 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 10.32% 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-05-19 01:25 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 21.93% of sampled CPU passed through vma_interval_tree_remove, with repeated thread backtraces show 1 thread(s) around 0x00007fa9b889a7d2 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-05-19 01:01 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 100.00% 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-05-18 22:21 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through ima_file_free, with repeated thread backtraces show 1 thread(s) around 0x00007f334669a7d2 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-05-18 21:42 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 6.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-05-18 21:24 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 6.84% 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-05-18 18:55 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 28.07% of sampled CPU passed through userfaultfd_unmap_complete, with repeated thread backtraces show 1 thread(s) around 0x00007fa9b889a7d2 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-05-18 18:33 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.97% 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-05-18 15:12 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 10.91% of sampled CPU passed through __memcg_slab_post_alloc_hook, with repeated thread backtraces show 1 thread(s) around 0x00007ff9cac9a7d2 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-05-18 13:57 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.30% 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-05-18 13:02 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 29.13% of sampled CPU passed through __vma_start_write, with repeated thread backtraces show 1 thread(s) around 0x00007fee4ee7b7d2 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-05-18 12:25 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through PreCommit_CheckForSerializationFailure, 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-05-18 12:06 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.21% of sampled CPU passed through folio_add_new_anon_rmap, 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-05-18 12:04 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 21.97% of sampled CPU passed through unmap_vmas, with repeated thread backtraces show 1 thread(s) around 0x00007f8fa7c9a7d2 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-05-18 09:57 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 5.62% 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-05-18 08:42 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 15.39% of sampled CPU passed through __memcg_slab_free_hook, with repeated thread backtraces show 1 thread(s) around 0x00007f263f69a7d2 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-05-18 05:56 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 59.49% of sampled CPU passed through __free_one_page, with repeated thread backtraces show 1 thread(s) around 0x00007fc38ce9a7d2 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-05-18 03:11 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through kmem_cache_free, with repeated thread backtraces show 1 thread(s) around 0x00007fc38ce9a7d2 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-05-18 01:58 UTC. Details · JSON

sshd-auth is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through do_syscall_64, 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-05-17 22:28 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 11.54% 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-05-17 19:59 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 28.08% of sampled CPU passed through unmap_page_range, with repeated thread backtraces show 1 thread(s) around 0x00007f9d21c9a7d2 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-05-17 18:13 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.20% 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-05-17 18:08 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 24.39% of sampled CPU passed through native_flush_tlb_one_user, with repeated thread backtraces show 1 thread(s) around 0x00007fc38ce9a7d2 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-05-17 16:54 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.45% of sampled CPU passed through verify_compact_attribute, 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-05-17 16:20 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 24.73% of sampled CPU passed through mas_wr_store_entry, with repeated thread backtraces show 1 thread(s) around 0x00007fdf0e29a7d2 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-05-16 05:51 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 10.93% 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-05-16 03:11 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.08% of sampled CPU passed through __lruvec_stat_mod_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-05-16 03:03 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-05-15 22:12 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-05-15 21:55 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 4.01% 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-05-15 19:00 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-05-15 18:05 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through nf_ct_get_tuple, with repeated thread backtraces show 1 thread(s) around 0x00007f9d21c9a7d2 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-05-15 15:53 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 23.56% of sampled CPU passed through __netlink_lookup, with repeated thread backtraces show 1 thread(s) around 0x00007f8df049a7d2 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-05-15 15:18 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 6.46% of sampled CPU passed through do_anonymous_page, 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-05-15 13:07 UTC. Details · JSON

dockerd is stuck in a likely socket churn loop: 10.98% of sampled CPU passed through futex_wake_mark, 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-05-15 08:33 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through validate_xmit_skb, with repeated thread backtraces show 1 thread(s) around 0x00007f18a6e9a7d2 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-05-15 08:15 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through PyObject_GC_Del, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () 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-05-15 03:34 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 5.36% 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-05-15 02:03 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 10.27% of sampled CPU passed through do_wp_page, 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-05-14 22:18 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f13c609a7d2 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-05-14 22:18 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through read_tsc, 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-05-14 21:26 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 20.65% of sampled CPU passed through get_pid_task, with repeated thread backtraces show 1 thread(s) around 0x00007f202289a7d2 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-05-14 21:04 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.18% 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-05-14 15:30 UTC. Details · JSON

python3.13 is stuck in a likely file not found retry loop: 8.35% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 2 thread(s) around 0x00007fecc1fabffe in ?? () from target:<path> and 1 thread(s) around 0x00007fecc201260a in fstatat64 () 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-05-14 13:02 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 10.60% 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-05-14 12:52 UTC. Details · JSON

sshd-auth is stuck in a likely timer churn loop: 100.00% of sampled CPU passed through dequeue_task_fair, with repeated thread backtraces show 1 thread(s) around 0x00007f251a09a7d2 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-05-14 12:43 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 10.58% of sampled CPU passed through __kmalloc_node_track_caller_noprof, with repeated thread backtraces show 1 thread(s) around 0x00007f202289a7d2 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-05-14 12:24 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 10.15% 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-05-14 09:44 UTC. Details · JSON

sshd-session is stuck in a likely socket churn loop: 21.96% of sampled CPU passed through native_flush_tlb_one_user, with repeated munmap x17, read x4, getpid x3.

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-05-14 08:41 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 10.33% 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-05-14 07:45 UTC. Details · JSON

dockerd is stuck in a likely socket churn loop: 100.00% of sampled CPU passed through do_epoll_wait, 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-05-14 05:54 UTC. Details · JSON

sshd-auth is stuck in a likely busy poll loop: 25.00% of sampled CPU passed through __smp_call_single_queue, 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-05-14 02:49 UTC. Details · JSON

dockerd is stuck in a likely socket churn loop: 53.32% of sampled CPU passed through __futex_hash, 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-05-14 02:27 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 9.84% of sampled CPU passed through xas_start, with repeated thread backtraces show 1 thread(s) around 0x00007f145209a7d2 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-05-14 01:31 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.29% 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-05-13 22:23 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 4.09% of sampled CPU passed through __memcg_kmem_charge_page, 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-05-13 20:56 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 10.55% 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-05-13 20:09 UTC. Details · JSON

dockerd is stuck in a likely socket churn loop: 50.00% of sampled CPU passed through unresolved offset, 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-05-13 19:35 UTC. Details · JSON

dockerd is stuck in a likely socket churn loop: 100.00% of sampled CPU passed through __schedule, 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-05-13 18:42 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 13.44% of sampled CPU passed through clear_page_erms, with repeated thread backtraces show 1 thread(s) around 0x00007f72c409a7d2 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-05-13 10:56 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through netlink_create, with repeated thread backtraces show 1 thread(s) around 0x00007fac17a9a7d2 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-05-13 09:36 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 27.47% of sampled CPU passed through inet6_dump_addr, with repeated thread backtraces show 1 thread(s) around 0x00007f3a8049a7d2 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-05-13 08:15 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.81% 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-05-13 08:14 UTC. Details · JSON

rsync is stuck in a likely busy poll loop: 6.00% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f95a089a7d2 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-05-13 06:39 UTC. Details · JSON

sshd-auth is stuck in a likely timer churn loop: 53.23% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f97dda9a7d2 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-05-13 06:39 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through generic_permission, 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-05-13 05:05 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.72% of sampled CPU passed through vma_alloc_folio_noprof, 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-05-13 04:01 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through PyUnicode_FromWideChar, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () 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-05-13 02:59 UTC. Details · JSON

redis-check-rdb is stuck in a likely busy poll loop: 5.11% of sampled CPU passed through __snprintf_chk@plt, 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-05-13 02:32 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 11.40% of sampled CPU passed through adler32_z, with repeated thread backtraces show 1 thread(s) around 0x00007f4cecc9a7d2 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-05-13 02:03 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through free_pcppages_bulk, 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-05-13 01:12 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 5.84% of sampled CPU passed through get_mem_cgroup_from_mm, 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-05-13 01:12 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 9.41% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f922f09a7d2 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-05-12 23:48 UTC. Details · JSON

rsync is stuck in a likely busy poll loop: 15.58% of sampled CPU passed through rep_movs_alternative, with repeated thread backtraces show 1 thread(s) around 0x00007f02c949a7d2 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-05-12 23:48 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.29% 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-05-12 22:29 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through _raw_spin_lock_irqsave, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () 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-05-12 19:05 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through fdget, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () 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-05-12 10:12 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.39% of sampled CPU passed through __rcu_read_lock, 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-05-12 09:43 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.62% 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-05-12 09:43 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 12.28% of sampled CPU passed through kfree, with repeated thread backtraces show 1 thread(s) around 0x00007f27fda9a7d2 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-05-12 09:43 UTC. Details · JSON

sshd-auth is stuck in a likely timer churn loop: 100.00% of sampled CPU passed through intel_iommu_map_pages, with repeated thread backtraces show 1 thread(s) around 0x00007f4ff3a9a7d2 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-05-12 06:27 UTC. Details · JSON