Random freezes on fedora 36 with AMD GPU

BOOT_IMAGE=(hd7,gpt4)/vmlinuz-5.19.8-200.fc36.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.luks.uuid=luks-a9ef7a03-5019-4d6a-beba-d98d832e5d4c rd.lvm.lv=fedora_localhost-live/swap rhgb quiet radeon.cik_support=0 amdgpu.cik_support=1

I also double-checked this on my last boot, and yet… inxi -Fzx:

  Device-1: AMD Oland XT [Radeon HD 8670 / R5 340X OEM R7 250/350/350X OEM]
    vendor: Dell driver: radeon v: kernel arch: GCN 1 bus-ID: 01:00.0
  Device-2: Logitech C920 PRO HD Webcam type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 3-5:4
  Display: wayland server: X.Org v: with: Xwayland v: 22.1.3
    compositor: gnome-shell driver: gpu: radeon resolution: 1: 1920x1080~60Hz
    2: 1920x1080~60Hz
  OpenGL: renderer: AMD OLAND (LLVM 14.0.0 DRM 2.50 5.19.8-200.fc36.x86_64)
    v: 4.5 Mesa 22.1.7 direct render: Yes

not sure why it’s not loading with the amdgpu driver. :confused:

Reread that:

1 Like

Alrighty! My bad. :stuck_out_tongue:

I just gave that a shot now that I’m back from vacay, hopefully it works!

So far that really seems to have helped, although I get some lockups here and there, they do seem to clear up without crashing and I have yet to have a completely insurmountable lockup with this configuration. I’m impressed!

In that case you can mark as a solution the post with amdgpu instructions.
Nonetheless, try to find the cause of lock-ups and report a bug (at least some logs), that should be easier, now that system recovers from a hang.

1 Like

I encountered a similar issue considering the hardware I’m using. So, whenever I stop working with my machine and it was idle for ~5 minutes it suddenly froze. It happened twice today and I just need to restart it to continue working.

   Kernel: 5.19.13-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
     v: 2.37-36.fc36 Desktop: GNOME v: 42.5 Distro: Fedora release 36 (Thirty
   Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x
     serial: <superuser required> UEFI: American Megatrends v: 5007
     date: 06/18/2019
   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball
     charge: 55% (should be ignored) status: discharging
   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: 1383 high: 1400 min/max: 1400/3700 boost: enabled
     cores: 1: 1400 2: 1397 3: 1400 4: 1400 5: 1276 6: 1397 7: 1397 8: 1400
     bogomips: 59093
   Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
   Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
     vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 bus-ID: 07:00.0
   Device-2: Z-Star Micro A4 tech USB2.0 Camera type: USB driver: uvcvideo
     bus-ID: 1-6:2
   Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X:
     loaded: amdgpu unloaded: fbdev,modesetting,vesa gpu: amdgpu
     resolution: 1360x768~60Hz
   OpenGL: renderer: AMD Radeon Vega 11 Graphics (raven LLVM 14.0.0 DRM 3.47
     5.19.13-200.fc36.x86_64) v: 4.6 Mesa 22.1.7 direct render: Yes
   Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: ASUSTeK PRIME
     B450M-A driver: snd_hda_intel bus-ID: 3-3:4 v: kernel bus-ID: 07:00.1
   Device-2: AMD Family 17h/19h HD Audio vendor: ASUSTeK PRIME B450M-A
     driver: snd_hda_intel v: kernel bus-ID: 07:00.6
   Device-3: JMTek LLC. Fantech Leviosa type: USB
     driver: hid-generic,snd-usb-audio,usbhid
   Sound Server-1: ALSA v: k5.19.13-200.fc36.x86_64 running: yes
   Sound Server-2: PulseAudio v: 15.0 running: no
   Sound Server-3: PipeWire v: 0.3.59 running: yes
   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
     vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: f000
     bus-ID: 05:00.0
   IF: enp5s0 state: down mac: <filter>
   Device-2: Realtek RTL8188EUS 802.11n Wireless Network Adapter type: USB
     driver: r8188eu bus-ID: 1-7:3
   IF: wlp1s0f0u7 state: up mac: <filter>
   Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
     driver: btusb v: 0.8 bus-ID: 1-9:5
   Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
   Local Storage: total: 698.65 GiB used: 35.17 GiB (5.0%)
   ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB
     temp: 37 C
   ID-2: /dev/sdb vendor: Toshiba model: MK5061GSYN size: 465.76 GiB
     temp: 36 C
   ID-1: / size: 231.3 GiB used: 20.76 GiB (9.0%) fs: btrfs dev: /dev/sda3
   ID-2: /boot size: 973.4 MiB used: 296.8 MiB (30.5%) fs: ext4
     dev: /dev/sda2
   ID-3: /boot/efi size: 598.8 MiB used: 13.9 MiB (2.3%) fs: vfat
     dev: /dev/sda1
   ID-4: /home size: 231.3 GiB used: 20.76 GiB (9.0%) fs: btrfs
     dev: /dev/sda3
   ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
   System Temperatures: cpu: 44.2 C mobo: N/A gpu: amdgpu temp: 44.0 C
   Fan Speeds (RPM): N/A
   Processes: 348 Uptime: 34m Memory: 13.58 GiB used: 2.99 GiB (22.0%)
   Init: systemd target: graphical (5) Compilers: gcc: 12.2.1 Packages: N/A
   note: see --rpm Shell: Zsh v: 5.8.1 inxi: 3.3.21

Update BIOS (a lot has changed over those three years) and start a new thread if this issue persists - you’ve got completely different hardware, it’s almost 10 years newer.

Same problem here: My cheap, plastic, Intel laptop is completely reliable, but my AMD A10-7800 APU daily working desktop is completely unreliable. Graphics just shut-down every several hours, and refuses to wake-up; must be re-booted, losing anything unsaved.

I’m an end–user in need of a reliable desktop. I’m not an IT guy, nor an enthusiast. So for me, Fedora is just not an option on AMD until this is fixed…I’m off to download OpenSUSE or Kubuntu. I’ll keep Fedora on the laptop, since I really like it; but this AMD/Fedora driver issue is untenable.


This is Kaveri APU with Sea Islands GPU, so you can use amgpu too:

If you’re here looking for some help, not just to complain, start a new thread with sudo inxi -Fmaz output and kernel/mesa version from distro that has no such issues on this computer.