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: 3-host issue family. Last seen 2026-10-22 19:20 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-10 22:15 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-10 21:55 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-11 16:12 UTC. Details · JSON

Repeated EGL/Mesa/Qt desktop warnings affected plasma-discover on KDE desktop 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: single-host issue family. Last seen 2026-07-11 16:12 UTC. Details · JSON

Repeated EGL/Mesa/Qt desktop warnings affected python3, displaycal-appl on desktop desktop 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: single-host issue family. Last seen 2026-07-11 16:12 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-10-22 19:20 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-09-19 18:54 UTC. Details · JSON

python3.13 is stuck in a likely unclassified userspace loop: 4.70% of sampled CPU passed through _PyEval_EvalFrameDefault, with repeated thread backtraces show 1 thread(s) around 0x00007fc1cb5849ee in __pthread_rwlock_wrlock_full64 () 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-09-20 04:49 UTC. Details · JSON

postgres is stuck in a likely file not found retry loop: 2.83% of sampled CPU passed through AllocSetCheck, with repeated thread backtraces show 1 thread(s) around 0x00007f95ab590687 in __GI__IO_adjust_column () from target:<path>.

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

Cluster size: 3-host issue family. Last seen 2026-09-20 04:49 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 21.64% of sampled CPU passed through do_sys_poll, with repeated thread backtraces show 1 thread(s) around 0x00007f70c809a7d2 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: 3-host issue family. Last seen 2026-09-20 02:02 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-10-05 15:22 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-10-22 19:20 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-10-22 19:28 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 10.43% of sampled CPU passed through truncate_inode_pages_range, with repeated thread backtraces show 1 thread(s) around 0x00007f2b2e89a7d2 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-10-22 19:28 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-10-22 19:28 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-09-20 03:00 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-09-20 02:40 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-09-19 16:33 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-09-19 16:33 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-09-19 16:33 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-09-19 16:33 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-09-19 16:33 UTC. Details · JSON

dockerd is stuck in a likely socket churn loop: 34.73% of sampled CPU passed through mem_cgroup_handle_over_high, 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-10-22 19:28 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through PreCommit_on_commit_actions, 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-10-22 19:28 UTC. Details · JSON

postgres is stuck in a likely timer churn loop: 100.00% of sampled CPU passed through start_dl_timer, 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-10-22 19:28 UTC. Details · JSON

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

sshd-session is stuck in a likely unclassified userspace loop: 8.81% of sampled CPU passed through __cxa_finalize@plt, with repeated thread backtraces show 1 thread(s) around 0x00007f8b3229a7d2 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-09-23 00:48 UTC. Details · JSON

sshd-auth is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through EVP_MD_fetch, 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-09-23 00:48 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through __update_load_avg_se, 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-09-23 00:19 UTC. Details · JSON

sshd-auth is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through alloc_iova_fast, 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-09-23 00:19 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through __x64_sys_sendto, with repeated thread backtraces show 1 thread(s) around 0x00007fc96349a7d2 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-09-22 23:53 UTC. Details · JSON

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

sshd-session is stuck in a likely unclassified userspace loop: 18.30% of sampled CPU passed through aa_sk_perm, with repeated thread backtraces show 1 thread(s) around 0x00007f0f5609a7d2 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-09-22 23:28 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through free_percpu, 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-09-22 22:31 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 11.73% of sampled CPU passed through native_read_msr, with repeated thread backtraces show 1 thread(s) around 0x00007f34adc9a7d2 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-09-22 22:31 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 24.61% of sampled CPU passed through free_unref_folios, with repeated thread backtraces show 1 thread(s) around 0x00007fab4a89a7d2 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-09-22 21:56 UTC. Details · JSON

sshd-session is stuck in a likely file not found retry loop: 100.00% of sampled CPU passed through sock_def_readable, with repeated thread backtraces show 1 thread(s) around 0x00007fa3b789a7d2 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-09-22 21:56 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-09-22 21:09 UTC. Details · JSON

sshd-auth is stuck in a likely timer churn loop: 100.00% of sampled CPU passed through __nf_conntrack_find_get, with repeated thread backtraces show 1 thread(s) around 0x00007f36be29a7d2 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-09-22 20:40 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through AtEOXact_Enum, 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-10-22 19:28 UTC. Details · JSON

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through perf_ctx_enable, with repeated thread backtraces show 1 thread(s) around 0x00007f82eb9e87d2 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-10-22 19:28 UTC. Details · JSON

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

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

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-10-22 19:28 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.33% of sampled CPU passed through __pte_offset_map_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-10-22 19:28 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through _PyEval_FrameClearAndPop, 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-10-22 19:28 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-10-22 19:20 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through read_tsc, 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-10-10 01:56 UTC. Details · JSON

python3.13 is stuck in a likely busy poll loop: 40.65% of sampled CPU passed through idle_cpu, 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-10-04 02:36 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through pfn_to_dma_pte, 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-09-21 04:19 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.88% 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-09-21 03:34 UTC. Details · JSON

sshd-auth is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through _raw_spin_lock, 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-09-21 02:02 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 8.22% 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-09-20 21:27 UTC. Details · JSON

python3.13 is stuck in a likely file not found retry loop: 5.58% of sampled CPU passed through _PyEval_EvalFrameDefault, with repeated thread backtraces show 1 thread(s) around __internal_syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:44.

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-09-20 20:47 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.18% 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-09-20 20:07 UTC. Details · JSON

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

postgres is stuck in a likely busy poll loop: 6.68% 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-09-20 18:04 UTC. Details · JSON

sshd-auth is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through syscall_return_via_sysret, 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-09-20 17:41 UTC. Details · JSON

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

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

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

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-09-20 17:00 UTC. Details · JSON

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

postgres is stuck in a likely busy poll loop: 8.12% 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-09-20 16:20 UTC. Details · JSON

sshd-auth is stuck in a likely timer churn loop: 100.00% of sampled CPU passed through unresolved offset, with repeated read x5, write x5, clock_nanosleep x2.

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-09-20 16:20 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-09-20 15:16 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-09-20 15:16 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-09-20 13:39 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-09-20 13:15 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-09-20 13:15 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-09-20 12:52 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-09-20 12:29 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-09-20 12:05 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-09-20 11:43 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-09-20 11:19 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-09-20 11:19 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-09-20 10:56 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-09-20 10:56 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-09-20 10:34 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-09-20 10:12 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-09-20 10:12 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-09-20 09:54 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-09-20 09:54 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-09-20 09:36 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-09-20 08:11 UTC. Details · JSON

postgres is stuck in a likely unclassified userspace loop: 2.27% of sampled CPU passed through hash_search_with_hash_value, with repeated thread backtraces show 1 thread(s) around 0x00007f2c8fb3d687 in _IO_adjust_column () 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-09-20 07:46 UTC. Details · JSON

sshd-session is stuck in a likely unclassified userspace loop: 8.36% of sampled CPU passed through adler32_z, with repeated thread backtraces show 1 thread(s) around 0x00007f3c9b09bcb2 in __libc_alloca_cutoff () 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-09-20 07:46 UTC. Details · JSON

rsync is stuck in a likely busy poll loop: 17.41% of sampled CPU passed through clear_page_erms, with repeated thread backtraces show 1 thread(s) around 0x00007f320e09bcb2 in __libc_alloca_cutoff () 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-09-20 07:13 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 1.25% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f1d1eab9687 in _IO_adjust_column () 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-09-20 06:32 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 3.08% of sampled CPU passed through AllocSetAlloc, with repeated thread backtraces show 1 thread(s) around 0x00007ff9bfdc1687 in _IO_adjust_column () 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-09-20 06:09 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 7.29% of sampled CPU passed through __mem_cgroup_charge, with repeated thread backtraces show 1 thread(s) around __internal_syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:44.

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-09-20 05:53 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 2.72% of sampled CPU passed through hash_search_with_hash_value, with repeated thread backtraces show 1 thread(s) around 0x00007f8443855687 in __GI__IO_adjust_column () 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-09-20 04:49 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-09-19 17:20 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-09-19 17:20 UTC. Details · JSON

postgres is stuck in a likely busy poll loop: 15.24% of sampled CPU passed through next_uptodate_folio, with repeated thread backtraces show 1 thread(s) around __internal_syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:44.

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-08-01 19:53 UTC. Details · JSON

ollama is stuck in a likely timer churn loop: 26.47% of sampled CPU passed through __check_object_size, 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-09-22 17:28 UTC. Details · JSON

postgres is stuck in a likely file not found retry loop: 4.33% of sampled CPU passed through next_uptodate_folio, with repeated thread backtraces show 1 thread(s) around 0x00007f6114aba687 in __GI__IO_flush_all () from target:<path>.

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

Cluster size: 3-host issue family. Last seen 2026-10-12 08:43 UTC. Details · JSON