Random System freeze and Kernel Panic

As of five days ago I have not been able to get rid of a random freeze and/or Kernel Panic. There don’t seem to be any consistency with what triggers it BUT if any program crashes a freeze will always occur

I have check SSD health, reseated RAM, tryed only one drive active, uninstalling most programs, run package updates through the GUI and terminal, going back to Fedora 43, clean install of F44, upgrading from F43 to F44, even install windows again to try and have the things as clean as possible for Fedora install . Nothing is squelching this problem

I’ve spent some time going through this forum but either a solution isn’t here or I’m just failing at finding it

I am still quite new to Linux so don’t know where to look or how to read any logs (I’ve looked at journalctl but quite frankly have no idea what i’m sifting through)

I’m guessing at this point its some missmatch of drive/hardware or a hardware issue, I just have no idea where/if fedora tells me whats happening

Any help or link to another topic that can would be appreciated

Currently running Fedora 44 KDE with all updates applied

1 Like

Welcome to Fedora Discourse :slight_smile:

Let’s start please by posting your system specs. especially RAM and graphics card.

In Konsole, run this command and post the output back here:

journalctl -b -1 -e

In your reply, highlight the terminal output and click on </> in the composer to wrap with preformatted text.

Thanks

1 Like

I’d run an overnight or 24 hours mem test making sure RAM is not defective.

2 Likes

System Specs are
AMD Ryzen 9 5950X 16-Core Processor
32GB RAM
AMD Radeon 6800

The out put of “journalctl -b -1 -e” is as follows

Stack trace of thread 4667:
                                                #0  0x00007f528ba80e32 __syscall_cancel_arch (libc.so.6 + 0x7be32)
                                                #1  0x00007f528ba7506c __internal_syscall_cancel (libc.so.6 + 0x7006c)
                                                #2  0x00007f528ba750b4 __syscall_cancel (libc.so.6 + 0x700b4)
                                                #3  0x00007f528baef8a6 ppoll (libc.so.6 + 0xea8a6)
                                                #4  0x00007f528ab5f065 n/a (/usr/lib64/libglib-2.0.so.0.8800.0 (deleted) + 0x48065)
                                                #5  0x00007f528ab5f123 n/a (/usr/lib64/libglib-2.0.so.0.8800.0 (deleted) + 0x48123)
                                                #6  0x00007f528c44b69d _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x44b69d)
                                                #7  0x00007f528c116083 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x116083)
                                                #8  0x00007f528c245556 _ZN7QThread4execEv (libQt6Core.so.6 + 0x245556)
                                                #9  0x00007f528c2f18f1 _ZN14QThreadPrivate5startEPv (libQt6Core.so.6 + 0x2f18f1)
                                                #10 0x00007f528ba78759 start_thread (libc.so.6 + 0x73759)
                                                #11 0x00007f528bafca4c __clone3 (libc.so.6 + 0xf7a4c)
                                                
                                                Stack trace of thread 18652:
                                                #0  0x00007f528ba80e32 __syscall_cancel_arch (libc.so.6 + 0x7be32)
                                                #1  0x00007f528ba7506c __internal_syscall_cancel (libc.so.6 + 0x7006c)
                                                #2  0x00007f528ba753b7 __GI___futex_abstimed_wait_cancelable64 (libc.so.6 + 0x703b7)
                                                #3  0x00007f528ba77e22 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x72e22)
                                                #4  0x00007f528c2fa2ce _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2fa2ce)
                                                #5  0x00007f528c249f27 _ZN17QThreadPoolThread3runEv (libQt6Core.so.6 + 0x249f27)
                                                #6  0x00007f528c2f18f1 _ZN14QThreadPrivate5startEPv (libQt6Core.so.6 + 0x2f18f1)
                                                #7  0x00007f528ba78759 start_thread (libc.so.6 + 0x73759)
                                                #8  0x00007f528bafca4c __clone3 (libc.so.6 + 0xf7a4c)
                                                
                                                Stack trace of thread 18653:
                                                #0  0x00007f528ba80e32 __syscall_cancel_arch (libc.so.6 + 0x7be32)
                                                #1  0x00007f528ba7506c __internal_syscall_cancel (libc.so.6 + 0x7006c)
                                                #2  0x00007f528ba753b7 __GI___futex_abstimed_wait_cancelable64 (libc.so.6 + 0x703b7)
                                                #3  0x00007f528ba77e22 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x72e22)
                                                #4  0x00007f528c2fa2ce _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2fa2ce)
                                                #5  0x00007f528c249f27 _ZN17QThreadPoolThread3runEv (libQt6Core.so.6 + 0x249f27)
                                                #6  0x00007f528c2f18f1 _ZN14QThreadPrivate5startEPv (libQt6Core.so.6 + 0x2f18f1)
                                                #7  0x00007f528ba78759 start_thread (libc.so.6 + 0x73759)
                                                #8  0x00007f528bafca4c __clone3 (libc.so.6 + 0xf7a4c)
                                                
                                                Stack trace of thread 4658:
                                                #0  0x00007f528ba80e32 __syscall_cancel_arch (libc.so.6 + 0x7be32)
                                                #1  0x00007f528ba7506c __internal_syscall_cancel (libc.so.6 + 0x7006c)
                                                #2  0x00007f528ba753b7 __GI___futex_abstimed_wait_cancelable64 (libc.so.6 + 0x703b7)
                                                #3  0x00007f528ba77c0c pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x72c0c)
                                                #4  0x00007f526d00010d cnd_wait (libgallium-26.0.5.so + 0x60010d)
                                                #5  0x00007f526cfb5eac util_queue_thread_func (libgallium-26.0.5.so + 0x5b5eac)
                                                #6  0x00007f526d00004c impl_thrd_routine (libgallium-26.0.5.so + 0x60004c)
                                                #7  0x00007f528ba78759 start_thread (libc.so.6 + 0x73759)
                                                #8  0x00007f528bafca4c __clone3 (libc.so.6 + 0xf7a4c)
                                                
                                                Stack trace of thread 18651:
                                                #0  0x00007f528ba80e32 __syscall_cancel_arch (libc.so.6 + 0x7be32)
                                                #1  0x00007f528ba7506c __internal_syscall_cancel (libc.so.6 + 0x7006c)
                                                #2  0x00007f528ba753b7 __GI___futex_abstimed_wait_cancelable64 (libc.so.6 + 0x703b7)
                                                #3  0x00007f528ba77e22 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x72e22)
                                                #4  0x00007f528c2fa2ce _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2fa2ce)
                                                #5  0x00007f528c249f27 _ZN17QThreadPoolThread3runEv (libQt6Core.so.6 + 0x249f27)
                                                #6  0x00007f528c2f18f1 _ZN14QThreadPrivate5startEPv (libQt6Core.so.6 + 0x2f18f1)
                                                #7  0x00007f528ba78759 start_thread (libc.so.6 + 0x73759)
                                                #8  0x00007f528bafca4c __clone3 (libc.so.6 + 0xf7a4c)
                                                
                                                Stack trace of thread 4696:
                                                #0  0x00007f528ba80e32 __syscall_cancel_arch (libc.so.6 + 0x7be32)
                                                #1  0x00007f528ba7506c __internal_syscall_cancel (libc.so.6 + 0x7006c)
                                                #2  0x00007f528ba750b4 __syscall_cancel (libc.so.6 + 0x700b4)
                                                #3  0x00007f528baef8a6 ppoll (libc.so.6 + 0xea8a6)
                                                #4  0x00007f528ab5f065 n/a (/usr/lib64/libglib-2.0.so.0.8800.0 (deleted) + 0x48065)
                                                #5  0x00007f528ab5f123 n/a (/usr/lib64/libglib-2.0.so.0.8800.0 (deleted) + 0x48123)
                                                #6  0x00007f528c44b69d _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x44b69d)
                                                #7  0x00007f528c116083 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x116083)
                                                #8  0x00007f528c245556 _ZN7QThread4execEv (libQt6Core.so.6 + 0x245556)
                                                #9  0x00007f528c2f18f1 _ZN14QThreadPrivate5startEPv (libQt6Core.so.6 + 0x2f18f1)
                                                #10 0x00007f528ba78759 start_thread (libc.so.6 + 0x73759)
                                                #11 0x00007f528bafca4c __clone3 (libc.so.6 + 0xf7a4c)
                                                ELF object binary architecture: AMD x86-64

I think there are more thread stack traces as I don’t see a thread with main() in it.

Do you have core dumps that you can analyse to see what it crashing?

What hardware do you have a desktopo of laptop?

Have you checked that your GPU is seated securely in its PCI slot?
I had an issue with my system that was fixed by reseating the GPU after cleaning the slot to remove any dust.

This pattern suggests a hardware problem. Your first priority should be to backup important data and make notes of the installed software and configuration changes so you are ready to configure a replacement.

RAM is the most common failure point. Use the standalone memtest86+ tester and run it overnight for several nights. Failure rates for desktop power supplies increase with age and can first appear as unstable output around 5 years. Laptops tend to have overheating due to old thermal paste and accumulated dust. There are many apps that allow you to monitor temperature sensors to see if freezes are associated with higher temperatures.

Before retiring I worked in a large enterprise where 5+ years old laptops with issues would just be replaced, those without issues at 7 years. Machines with issues would be replaced with spares while IT attempted repairs during periods when there were no pressing demands on their time.

I will check the GPU slot when I get home from work tonight

AND I will look into running memtest86+

Side note : I ran the “journalctl -b -1 -e” command again and got different output not sure why or how but out put is bellow

May 07 21:02:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-51C9\x2d74C1 comm="systemd" exe="/usr/lib/sys>
May 07 21:02:47 fedora kernel: audit: type=1131 audit(1778151767.525:926): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-51C9\x2d74C1 com>
May 07 21:02:47 fedora kernel: EXT4-fs (sda2): unmounting filesystem 715f2659-5240-41ea-a03a-2cf50d6f1801.
May 07 21:02:47 fedora systemd[1]: boot.mount: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Unmounted boot.mount - /boot.
May 07 21:02:47 fedora systemd[1]: systemd-fsck@dev-disk-by\x2duuid-715f2659\x2d5240\x2d41ea\x2da03a\x2d2cf50d6f1801.service: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Stopped systemd-fsck@dev-disk-by\x2duuid-715f2659\x2d5240\x2d41ea\x2da03a\x2d2cf50d6f1801.service - File System Check on /dev/disk/by-uuid/715f2659-5240-41ea-a03a-2cf50d6f1801.
May 07 21:02:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-715f2659\x2d5240\x2d41ea\x2da03a\x2d2cf50d6f1>
May 07 21:02:47 fedora systemd[1]: Removed slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
May 07 21:02:47 fedora systemd[1]: Stopped target local-fs-pre.target - Preparation for Local File Systems.
May 07 21:02:47 fedora kernel: audit: type=1131 audit(1778151767.534:927): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-715f2659\x2d5240>
May 07 21:02:47 fedora systemd[1]: Stopping lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
May 07 21:02:47 fedora systemd[1]: systemd-remount-fs.service: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Stopped systemd-remount-fs.service - Remount Root and Kernel File Systems.
May 07 21:02:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? ad>
May 07 21:02:47 fedora systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Stopped systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
May 07 21:02:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostn>
May 07 21:02:47 fedora systemd[1]: systemd-tmpfiles-setup-dev-early.service: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Stopped systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully.
May 07 21:02:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev-early comm="systemd" exe="/usr/lib/systemd/systemd">
May 07 21:02:47 fedora kernel: audit: type=1131 audit(1778151767.535:928): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/s>
May 07 21:02:47 fedora kernel: audit: type=1131 audit(1778151767.535:929): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/u>
May 07 21:02:47 fedora kernel: audit: type=1131 audit(1778151767.535:930): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev-early comm="systemd" e>
May 07 21:02:47 fedora systemd[1]: dev-disk-by\x2dlabel-zram0.swap: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Deactivated swap dev-disk-by\x2dlabel-zram0.swap - /dev/disk/by-label/zram0.
May 07 21:02:47 fedora systemd[1]: dev-disk-by\x2ddiskseq-6.swap: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Deactivated swap dev-disk-by\x2ddiskseq-6.swap - /dev/disk/by-diskseq/6.
May 07 21:02:47 fedora systemd[1]: dev-disk-by\x2duuid-32575a9c\x2d9a28\x2d43f8\x2d9f3f\x2d1ec16dd6c65d.swap: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Deactivated swap dev-disk-by\x2duuid-32575a9c\x2d9a28\x2d43f8\x2d9f3f\x2d1ec16dd6c65d.swap - /dev/disk/by-uuid/32575a9c-9a28-43f8-9f3f-1ec16dd6c65d.
May 07 21:02:47 fedora systemd[1]: dev-zram0.swap: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Deactivated swap dev-zram0.swap - Compressed Swap on /dev/zram0.
May 07 21:02:47 fedora systemd[1]: Reached target umount.target - Unmount All Filesystems.
May 07 21:02:47 fedora systemd[1]: Stopping systemd-zram-setup@zram0.service - Create swap on /dev/zram0...
May 07 21:02:47 fedora kernel: zram0: detected capacity change from 16777216 to 0
May 07 21:02:47 fedora (udev-worker)[22356]: zram0: Failed to process device, ignoring: Device or resource busy
May 07 21:02:47 fedora systemd[1]: lvm2-monitor.service: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Stopped lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
May 07 21:02:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? t>
May 07 21:02:47 fedora kernel: audit: type=1131 audit(1778151767.589:931): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd>
May 07 21:02:47 fedora systemd[1]: systemd-zram-setup@zram0.service: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Stopped systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
May 07 21:02:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-zram-setup@zram0 comm="systemd" exe="/usr/lib/systemd/systemd" hostnam>
May 07 21:02:47 fedora systemd[1]: Removed slice system-systemd\x2dzram\x2dsetup.slice - Slice /system/systemd-zram-setup.
May 07 21:02:47 fedora systemd[1]: Reached target shutdown.target - System Shutdown.
May 07 21:02:47 fedora systemd[1]: Reached target final.target - Late Shutdown Services.
May 07 21:02:47 fedora systemd[1]: systemd-poweroff.service: Deactivated successfully.
May 07 21:02:47 fedora systemd[1]: Finished systemd-poweroff.service - System Power Off.
May 07 21:02:47 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? add>
May 07 21:02:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr>
May 07 21:02:47 fedora systemd[1]: Reached target poweroff.target - System Power Off.
May 07 21:02:47 fedora systemd[1]: Shutting down.
May 07 21:02:47 fedora audit: BPF prog-id=57 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=56 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=61 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=60 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=75 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=74 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=45 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=47 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=46 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=65 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=64 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=48 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=50 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=49 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=53 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=52 op=UNLOAD
May 07 21:02:47 fedora audit: BPF prog-id=41 op=UNLOAD
May 07 21:02:47 fedora systemd-shutdown[1]: Syncing filesystems and block devices.
May 07 21:02:47 fedora systemd-shutdown[1]: Sending SIGTERM to remaining processes...
May 07 21:02:47 fedora systemd-journald[1119]: Journal stopped

So I ran memtest86+ and..well.. I think its the ram

Thanks you guys from the directions to help diagnose the issue

1 Like

Double check if frequencies are set ok, and RAM is not overclocked. Looks like you have DDR4 capable of 2133 MHz. What’s the operating frequency set to? Make sure to set the freq in the BIOS within the range of specs of the RAM and re-run the test.

1 Like