Fedora 40 KDE system freezes/locks up after an hour or 2

Ask Fedora
, , , , , , , , ,
1

I’m pretty new to Linux and just switched away from Windows, everything has been working great except I’ve been experiencing an issue where after an hour or 2, the PC completely freezes and locks up. None of the keys or commands seem to work and I am unable to resolve the issue. What are the steps I should perform in order to fix the issue? Not sure what command or logs I should use.

  Kernel: 6.10.4-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: KDE Plasma v: 6.1.4 Distro: Fedora Linux 40 (KDE Plasma)
Machine:
  Type: Desktop Mobo: Micro-Star model: B550M PRO-VDH WIFI (MS-7C95) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 2.I0
    date: 10/10/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2
    rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
  Speed (MHz): avg: 2957 high: 4200 min/max: 2200/4208 boost: enabled cores:
    1: 4199 2: 2200 3: 3696 4: 2100 5: 2100 6: 4200 7: 4197 8: 2200 9: 4200
    10: 2100 11: 2099 12: 2200 bogomips: 86406
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
    vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 bus-ID: 2d:00.0
  Device-2: MACROSILICON UGREEN HDMI Capture
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB bus-ID: 3-4:3
  Device-3: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
    type: USB bus-ID: 5-2.3:6
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.2
    compositor: kwin_wayland driver: N/A resolution: 1: 2560x1080 2: 1920x1080
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms:
    active: gbm,wayland,x11,surfaceless,device inactive: N/A
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.5 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 6750 XT (radeonsi navi22 LLVM
    18.1.6 DRM 3.57 6.10.4-200.fc40.x86_64)
  API: Vulkan v: 1.3.283 drivers: N/A surfaces: xcb,xlib,wayland devices: 2
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
    bus-ID: 2d:00.1
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 2f:00.4
  Device-3: MACROSILICON UGREEN HDMI Capture
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB bus-ID: 3-4:3
  Device-4: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
    type: USB bus-ID: 5-2.3:6
  Device-5: Frys EDIFIER R19U driver: hid-generic,snd-usb-audio,usbhid
    type: USB bus-ID: 5-4:5
  API: ALSA v: k6.10.4-200.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: active
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel bus-ID: 29:00.0
  IF: wlo1 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel port: f000 bus-ID: 2a:00.0
  IF: enp42s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb v: 0.8 type: USB
    bus-ID: 1-9:5
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 5 TiB used: 3.05 TiB (61.0%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G2B0C-00PXH0
    size: 465.76 GiB temp: 39.9 C
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    temp: 36.9 C
  ID-3: /dev/sda vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB
  ID-4: /dev/sdb vendor: Western Digital model: WDS100T2B0A-00SM50
    size: 931.51 GiB
  ID-5: /dev/sdc vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB
Partition:
  ID-1: / size: 929.93 GiB used: 479.21 GiB (51.5%) fs: btrfs
    dev: /dev/nvme1n1p3
  ID-2: /boot size: 973.4 MiB used: 410 MiB (42.1%) fs: ext4
    dev: /dev/nvme1n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19 MiB (3.2%) fs: vfat
    dev: /dev/nvme1n1p1
  ID-4: /home size: 929.93 GiB used: 479.21 GiB (51.5%) fs: btrfs
    dev: /dev/nvme1n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.9 C mobo: N/A gpu: amdgpu temp: 51.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 1010
Info:
  Memory: total: 32 GiB available: 31.26 GiB used: 5.14 GiB (16.5%)
  Processes: 569 Uptime: 27m Init: systemd target: graphical (5)
  Packages: 43 Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.26 inxi: 3.3.34
2

The inxi report is a good start. Additional troubleshooting steps:

  • make sure the system is fully updated so you aren’t chasing a solved problem
  • run a monitoring tool such as htop that shows memory and CPU usage. Freezes are often associated with a program attempting to allocate huge amounts of RAM space.
  • journalctl captures enormous amounts of detail, which means there is a good chance there will be entries related to your problem, but finding them can be a “needle in haystack” exercise. Focus on high priority errors and the times the problems occured. It is useful to just browse the journalctl output for a few previous boot sessions to get an idea of the overall flow, then compare a normal session to one that froze. If you have not used journalctl, you can find many examples in this forum. Read man journalctl for explanations.
  • check if the problem occurs removing all non-essential hardware. Linux often has problems with ad-on hardware whose drivers may not keep up with changes to the kernel.
  • check KDE forums for similalr reports. Many linux problems are specific to a certain combination of hardware and software and will affect multiple distros.
3

System is up to date, I’ve used htop but when the freeze occurred it didn’t show anything. Is there a recommended specific journalctl command I can use for? I’m gonna post journalctl -b -p err here is the error: journalctl -b -p err

4

Probably more reasonable to use journalctl -b -1 since the data you would be looking for would be in the logs from the last boot where the freeze occurred, not the current one. Then scan the times to see what was reported just before or at the time it locked up. That data would be necessary.

I see a core dump in the log you posted. It also appears that you were running steam when that data was generated.

Logs segments that are short enough to paste into the post should be entered here, using the preformatted text button </> on the toolbar to retain on-screen formatting so they are more readable. Most of the on line log repos only keep the data for a very short time. so that data is quickly lost if not pasted directly into the post here.