Fresh install Fedora 41 constantly freezes

Just did a fresh installation of Fedora Workstatin 41, and it keep getting freezes, to the point I have to hold the power button to shutdown the PC. When the freeze occurs, the keyboard seems functional (numlock/capslock leds responds), but hitting Ctrl+Alt+F2/F3 etc. to get into console doesn’t work.

The freeze is happening in both kernel 6.11 and 6.12. I also didn’t notice any load on memory or CPU when the freeze accur. It’s running on Wayland on a 75Hz monitor.

The only thing I’ve noticed is that I think it only happened when I had music.youtube.com playing, not really sure though.

System specs:

System:
  Kernel: 6.11.4-301.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: GNOME v: 47.3 tk: GTK v: 3.24.43 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 41 (Workstation Edition)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B450M-GAMING/BR v: Rev X.0x
    serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 1823
    date: 10/15/2019
CPU:
  Info: quad core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64
    type: MT MCP arch: Zen/Zen+ note: check rev: 1 cache: L1: 384 KiB L2: 2 MiB
    L3: 4 MiB
  Speed (MHz): avg: 4117 min/max: 1400/3700 boost: enabled cores: 1: 4117
    2: 4117 3: 4117 4: 4117 5: 4117 6: 4117 7: 4117 8: 4117 bogomips: 59088
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega
    Series / Radeon Mobile Series] vendor: ASUSTeK driver: amdgpu v: kernel
    arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: HDMI-A-1
    empty: DP-1,DVI-D-1 bus-ID: 09:00.0 chip-ID: 1002:15d8 temp: 48.0 C
  Display: wayland server: Xwayland v: 24.1.4 compositor: gnome-shell
    driver: gpu: amdgpu display-ID: 0
  Monitor-1: HDMI-A-1 model: LG (GoldStar) ULTRAWIDE res: 2560x1080 dpi: 81
    diag: 869mm (34.2")
  API: OpenGL v: 4.6 vendor: amd mesa v: 24.3.3 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon Vega 11 Graphics (radeonsi raven
    LLVM 19.1.5 DRM 3.59 6.11.4-301.fc41.x86_64) device-ID: 1002:15d8
    display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
    Audio vendor: ASUSTeK PRIME B450M-A driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 09:00.1 chip-ID: 1002:15de
  Device-2: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: ASUSTeK PRIME B450M-A driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 09:00.6 chip-ID: 1022:15e3
  API: ALSA v: k6.11.4-301.fc41.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL8192EE PCIe Wireless Network Adapter driver: rtl8192ee
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 04:00.0
    chip-ID: 10ec:818b
  IF: wlp4s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 07:00.0 chip-ID: 10ec:8168
  IF: enp7s0 state: down mac: <filter>
Drives:
  Local Storage: total: 1.02 TiB used: 10.59 GiB (1.0%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SNV2S1000G size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 26.9 C
  ID-2: /dev/sda vendor: SanDisk model: SSD PLUS 120GB size: 111.8 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 26 C
Partition:
  ID-1: / size: 734.6 GiB used: 10.31 GiB (1.4%) fs: btrfs dev: /dev/nvme0n1p5
  ID-2: /boot size: 973.4 MiB used: 264.4 MiB (27.2%) fs: ext4
    dev: /dev/nvme0n1p4
  ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 48.4 C mobo: N/A gpu: amdgpu temp: 48.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 13.57 GiB used: 4.35 GiB (32.0%)
  Processes: 384 Power: uptime: 22m wakeups: 0 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 10
    Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.32 running-in: ptyxis-agent
    inxi: 3.3.37

journalctl -b 0 -p 3:

Jan 28 07:43:08 fedora kernel: amdgpu 0000:09:00.0: amdgpu: Secure display: Generic Failure.
Jan 28 07:43:08 fedora kernel: amdgpu 0000:09:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jan 28 10:43:12 rafael-linux kernel: rtl8192ee: chksum report fail! REG_MCUFWDL:0x00070600
Jan 28 10:43:24 rafael-linux wpa_supplicant[1109]: bgscan simple: Failed to enable signal strength monitoring
Jan 28 10:43:24 rafael-linux gdm-password][1904]: gkr-pam: unable to locate daemon control file
Jan 28 10:43:25 rafael-linux systemd[1943]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2187.scope - Application launched by gnome-session-binary.
Jan 28 10:43:25 rafael-linux systemd[1943]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2189.scope - Application launched by gnome-session-binary.
Jan 28 10:43:25 rafael-linux systemd[1943]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-2193.scope - Application launched by gnome-session-binary.

journalctl -b 1 -p 3:

Jan 21 09:58:37 fedora kernel: amdgpu 0000:09:00.0: amdgpu: Secure display: Generic Failure.
Jan 21 09:58:37 fedora kernel: amdgpu 0000:09:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jan 21 12:58:39 fedora systemd-udevd[712]: /usr/lib/udev/rules.d/61-gdm.rules:41 GOTO="gdm_hybrid_nvidia_laptop_check" has no matching label, ignoring.
Jan 21 12:58:40 fedora systemd-homed[930]: Failed to open /var/cache/systemd/home/: Permission denied
Jan 21 12:58:40 fedora alsactl[969]: /usr/sbin/alsactl: load_state:1689: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
Jan 21 12:59:36 fedora gdm-password][2406]: gkr-pam: unable to locate daemon control file
Jan 21 12:59:36 fedora gdm[1467]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jan 21 12:59:37 fedora systemd[2417]: Failed to start app-gnome-xdg\x2duser\x2ddirs-2583.scope - Application launched by gnome-session-binary.
Jan 21 12:59:40 fedora gdm[1467]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jan 21 13:01:20 fedora wpa_supplicant[1119]: bgscan simple: Failed to enable signal strength monitoring
Jan 21 13:06:47 fedora kernel: UBSAN: array-index-out-of-bounds in drivers/net/wireless/realtek/rtlwifi/btcoexist/halbtc8192e2ant.c:3005:36
Jan 21 13:06:47 fedora kernel: index 10 is out of range for type 'u8 [10]'
Jan 21 13:19:08 fedora systemd[1]: Failed to start systemd-binfmt.service - Set Up Additional Binary Formats.
Jan 21 13:27:35 fedora gdm[1467]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jan 21 13:27:37 fedora dbus-broker-launch[914]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Jan 21 13:27:37 fedora dbus-broker-launch[914]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Jan 21 13:27:37 fedora dbus-broker-launch[914]: Activation request for 'org.freedesktop.nm_dispatcher' failed.

journalctl -b 2 -p 3:

Jan 22 05:06:13 fedora kernel: amdgpu 0000:09:00.0: amdgpu: Secure display: Generic Failure.
Jan 22 05:06:13 fedora kernel: amdgpu 0000:09:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jan 22 08:06:21 fedora wpa_supplicant[1144]: bgscan simple: Failed to enable signal strength monitoring
Jan 22 08:06:57 fedora gdm-password][2056]: gkr-pam: unable to locate daemon control file
Jan 22 08:06:59 fedora systemd[2086]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2229.scope - Application launched by gnome-session-binary.
Jan 22 08:06:59 fedora systemd[2086]: Failed to start app-gnome-xdg\x2duser\x2ddirs-2254.scope - Application launched by gnome-session-binary.
Jan 22 08:07:00 fedora systemd[2086]: Failed to start app-gnome-spice\x2dvdagent-2403.scope - Application launched by gnome-session-binary.
Jan 22 09:21:00 rafael-linux sudo[20690]: pam_unix(sudo:auth): conversation failed
Jan 22 09:21:00 rafael-linux sudo[20690]: pam_unix(sudo:auth): auth could not identify password for [rafael]
Jan 22 09:57:44 rafael-linux systemd-coredump[34609]: [🡕] Process 7960 (Discord) of user 1000 dumped core.
                                                      
                                                      Stack trace of thread 173:
                                                      #0  0x00007f339d9dadb4 n/a (n/a + 0x0)
                                                      #1  0x00007f339d98208e n/a (n/a + 0x0)
                                                      #2  0x00007f339d969882 n/a (n/a + 0x0)
                                                      #3  0x00007f330efc79b3 n/a (n/a + 0x0)
                                                      ELF object binary architecture: AMD x86-64
Jan 22 09:57:46 rafael-linux gdm-password][35348]: gkr-pam: unable to locate daemon control file
Jan 22 09:57:47 rafael-linux systemd[2086]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-35459.scope - Application launched by gnome-session-binary.
Jan 22 09:57:47 rafael-linux systemd[2086]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-35460.scope - Application launched by gnome-session-binary.
Jan 22 09:57:47 rafael-linux systemd[2086]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-35466.scope - Application launched by gnome-session-binary.
Jan 22 10:05:52 rafael-linux kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [kworker/u32:1:29287]
Jan 22 10:05:52 rafael-linux kernel: CPU#3 Utilization every 4s during lockup:
Jan 22 10:05:53 rafael-linux kernel:         #1:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 22 10:05:53 rafael-linux kernel:         #2:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 22 10:05:53 rafael-linux kernel:         #3:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 22 10:05:53 rafael-linux kernel:         #4:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 22 10:05:53 rafael-linux kernel:         #5:   2% system,          0% softirq,          0% hardirq,          0% idle

Thanks in advance!

1 Like

Do you have another system you can try to ssh into the frozen system from?

1 Like

Yes I could borrow one, you want me to ssh and run journalctl -b 0 -p 3 ?

1 Like

use brave or other browser

This is the result of journalctl -b 0 -p 0..3 from ssh after a minute of the freeze:

Jan 28 07:43:08 fedora kernel: amdgpu 0000:09:00.0: amdgpu: Secure display: Generic Failure.
Jan 28 07:43:08 fedora kernel: amdgpu 0000:09:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jan 28 10:43:12 rafael-linux kernel: rtl8192ee: chksum report fail! REG_MCUFWDL:0x00070600
Jan 28 10:43:24 rafael-linux wpa_supplicant[1109]: bgscan simple: Failed to enable signal strength monitoring
Jan 28 10:43:24 rafael-linux gdm-password][1904]: gkr-pam: unable to locate daemon control file
Jan 28 10:43:25 rafael-linux systemd[1943]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2187.scope - Application launched by gnome-session-binary.
Jan 28 10:43:25 rafael-linux systemd[1943]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2189.scope - Application launched by gnome-session-binary.
Jan 28 10:43:25 rafael-linux systemd[1943]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-2193.scope - Application launched by gnome-session-binary.
Jan 28 12:41:41 rafael-linux kernel: amdgpu 0000:09:00.0: amdgpu: ring gfx timeout, signaled seq=884033, emitted seq=884035
Jan 28 12:41:41 rafael-linux kernel: amdgpu 0000:09:00.0: amdgpu: Process information: process gnome-system-mo pid 53595 thread gnome-system-mo pid 53595
Jan 28 12:41:42 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:41:45 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:41:47 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:41:49 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:41:58 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:01 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:02 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:06 rafael-linux kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [kworker/u32:6:50666]
Jan 28 12:42:06 rafael-linux kernel: CPU#5 Utilization every 4s during lockup:
Jan 28 12:42:06 rafael-linux kernel:         #1:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 28 12:42:06 rafael-linux kernel:         #2:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 28 12:42:06 rafael-linux kernel:         #3:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 28 12:42:06 rafael-linux kernel:         #4:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 28 12:42:06 rafael-linux kernel:         #5:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 28 12:42:10 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:12 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:12 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:14 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:15 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:23 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:30 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:34 rafael-linux kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 52s! [kworker/u32:6:50666]
Jan 28 12:42:34 rafael-linux kernel: CPU#5 Utilization every 4s during lockup:
Jan 28 12:42:34 rafael-linux kernel:         #1:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 28 12:42:34 rafael-linux kernel:         #2:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 28 12:42:34 rafael-linux kernel:         #3:   2% system,          0% softirq,          0% hardirq,          0% idle
Jan 28 12:42:34 rafael-linux kernel:         #4:   2% system,          1% softirq,          0% hardirq,          0% idle
Jan 28 12:42:34 rafael-linux kernel:         #5:   2% system,          0% softirq,          1% hardirq,          0% idle
Jan 28 12:42:35 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:41 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:42 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
Jan 28 12:42:46 rafael-linux pipewire[2182]: spa.alsa: front:1p: snd_pcm_mmap_commit error: Broken pipe
1 Like

This is bad…

And this is also bad…

You have a hardware problem. First easy thing to test is your memory.
Install memtest and run it overnight to see a problem is found.

1 Like

The fact that I was using Windows 10 without any issues doesn’t say anything? The only thing I’ve changed was the SSD.

Could be that the kernel and drivers just hit your hardware in different ways than Windows. Or Windows kernel and drivers ignore such problems more frequently (or are able to recover from such issues more easily).

2 Likes

Tried that, no luck.

Well, looks like I’m gonna go back to Windows then unfortunately.

Thanks everyone.

1 Like

Your hardware problems (if indeed you have which is very possible) will still be there. They may get worse as time goes one. Even if you change back to Windows, I would still run testing.

1 Like

It’s likely not a hardware problem in itself but a bug in the AMD firmware. There are a few bugs related to the GPU ring currently that aren’t fixed yet, you can find them back here:

Most of the GPU ring issues relate to hardware accelerated video rendering, disabling that in the browser/app will likely reduce the freezes.

3 Likes

it’s probably a mesa bug, and a fix is in the queue and should be available tomorrow via the updates-testing repo
Then this page will have a dnf command how to upgrade Mesa on your system.

https://bodhi.fedoraproject.org/updates/FEDORA-2025-a24369766c

You can also already download the rpm packages from koji
https://koji.fedoraproject.org/koji/buildinfo?buildID=2648922

1 Like

Disabling hardware acceleration worked as a temporary fix, been using for a few hours without any crash, thanks!

1 Like

Updated mesa to 24.3.4-3.fc41, and re-enabled all hardware acceleration, no freezes anymore. Problem solved.

Thank you very much.

1 Like

one question: does the command eglinfo produce a core dump?

I have the same problem on my Elitedesk with AMD CPU. Fedora freezes and have to shut down with power button. Computer has been running Windows without any problem

I have exactly the same issue. Even though I have run this command, the problem is still there:
sudo dnf upgrade --refresh --advisory=FEDORA-2025-a24369766c

This started after the latest version of Fedora 41, and the last few days have been terrible—so many shutdowns, and nothing works like it did before without any issues at all.

I’ve also noticed that this only happens when I have YouTube Music running in the background and am using Chrome.

journalctl -b 0 -p 0..3 | grep 'amdgpu'
Feb 03 11:56:10 fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=6, emitted seq=7
Feb 03 11:56:10 fedora kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process gst-plugin-scan pid 3015 thread gst-plugin:cs0 pid 3053
Module libdrm_amdgpu.so.1 from rpm libdrm-2.4.124-1.fc41.x86_64
#7 0x00007f2625bbba80 _ZL30amdgpu_ctx_set_sw_reset_statusP17radeon_winsys_ctx17pipe_reset_statusPKcz (libgallium-24.3.4.so + 0x9bba80)
#8 0x00007f2625bbef10 _Z19amdgpu_cs_submit_ibILb0EEvPvS0_i (libgallium-24.3.4.so + 0x9bef10)
#3 0x00007f2625bbd9bc _ZL15amdgpu_cs_flushP13radeon_cmdbufjPP17pipe_fence_handle (libgallium-24.3.4.so + 0x9bd9bc)
Feb 03 11:56:14 fedora abrt-notification[3739]: Process 4392 (gnome-shell) crashed in amdgpu_ctx_create(radeon_winsys*, radeon_ctx_priority, bool)()

The output of eglinfo: EGL client extensions string: EGL_EXT_client_extensions, EGL_EXT_device_bas - Pastebin.com

The mesa update is in the main repository, just run sudo dnf update to update it. Also if it doesn’t work you’re better off creating another thread.

I have already updated to the latest version of Fedora 41, so the issue is still there.

I also have the same problem on my Thinkpad A485 laptop with AMD CPU. Fedora freezes and have to shut down with power button.

1 Like