System instability on zen kernel after upgrading cpu from r7 3700x to r7 5700x3dT

Two days ago I upgraded my cpu from an amd R7 3700X to an amd r7 5700x. Shortly after upgrading the cpu, I started noticing numerous issues with my system including my internet browser crashing every 5 minutes, discord losing internet access, my internet browser not being able to load web pages, commands entered into the terminal would hang indefinitely, using KDE's log out functionality and logging back in would result in an indefinite black screen with no desktop, KDEs restart and shut down commands did not fully shut down and power off the system, they would shut it down enough that the monitors would detect no signal but it would remain powered on indefinitely (and wouldn't restart when the restart function was used). The stability issues were so widespread and so frequent I had to fully shut down using the physical power button and reboot every 15 minutes or so and couldn't effectively troubleshoot anything because even attempting to access log files would cause it to break badly enough to reboot.

For a while I thought the stability issues may have been due to some software changes (I tried to install cachyOS repo and kernels but had issues with linux-cachyos not being installed in the correct location) I made after upgrading the CPU, I have since reverted to an earlier snapshot so the software is unlikely the case, but my efforts to troubleshoot the software led to me trying out a different kernel. I installed the linux-amd kernel and switched over to that kernel, and have been running it for a full day with none of the issues I was experiencing on the stock linux-zen kernel.

I am using the same motherboard as I was using before, the BIOS was updated to the latest revision, which has support for the 5800x3d, a week prior to the cpu upgrade and I experienced no issues between then and installing the new cpu.

I suspected that there is something architecture specific that is off in my install of linux-zen considering that the 5800x3d has been out for a few months and I am not seeing any other stability issues related to a 5800x3d on the garuda forums, so I tried reinstalling with sudo pacman -S linux-zen linux-zen-headers followed by sudo update-grub, but rebooting into the linux-zen kernel after doing that brought back the stability issues. Does anyone have any ideas on how to resolve the issues with my zen kernel?

System:
Kernel: 6.0.2-AMD arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/vmlinuz-linux-amd
root=UUID=c1150b4d-37fd-45ba-891c-c970b4133d9c rw [email protected]
amd_iommu=on vfio-pci.ids=1002:687f,1002:aaf8 iommu=pt video=efifb:off
cryptdevice=UUID=fdeba41a-daf3-4497-ad26-81235b8d841f:luks-fdeba41a-daf3-4497-ad26-81235b8d841f
root=/dev/mapper/luks-fdeba41a-daf3-4497-ad26-81235b8d841f splash
rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1
resume=/dev/mapper/luks-317c8a85-28be-4c8e-b38d-98f1eb5cd257 loglevel=3
video=efif:off quiet
Desktop: KDE Plasma v: 5.26.1 tk: Qt v: 5.15.6 wm: kwin_wayland vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-F GAMING v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 4403
date: 04/27/2022
CPU:
Info: model: AMD Ryzen 7 5800X3D bits: 64 type: MT MCP arch: Zen 3 gen: 4
level: v3 note: check built: 2021-22 process: TSMC n7 (7nm)
family: 0x19 (25) model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 96 MiB desc: 1x96 MiB
Speed (MHz): avg: 2617 high: 3594 min/max: 2200/4549 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2200 2: 2200
3: 2879 4: 2872 5: 3594 6: 2878 7: 3588 8: 2200 9: 2200 10: 2200 11: 2200
12: 2875 13: 2200 14: 2200 15: 2200 16: 3400 bogomips: 108860
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M] vendor: Tul
/ PowerColor driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-1,DP-2,HDMI-A-1 empty: DP-3 bus-ID: 0c:00.0
chip-ID: 1002:73df class-ID: 0300
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu d-rect: 7040x1440 display-ID: 0
Monitor-1: DP-1 pos: center res: 2560x1440 size: N/A modes: N/A
Monitor-2: DP-2 pos: right res: 2560x1440 size: N/A modes: N/A
Monitor-3: HDMI-A-1 pos: primary,left res: 1920x1080 size: N/A modes: N/A
OpenGL: renderer: AMD Radeon RX 6700 XT (navi22 LLVM 14.0.6 DRM 3.48
6.0.2-AMD) v: 4.6 Mesa 22.2.1 direct render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
bus-ID: 1-1.4:5 pcie: gen: 4 chip-ID: 1532:0511 class-ID: 0300
speed: 16 GT/s serial: <filter> lanes: 16 bus-ID: 0c:00.1
chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Razer USA RZ19-0229 Gaming Microphone type: USB
driver: hid-generic,snd-usb-audio,usbhid
Sound API: ALSA v: k6.0.2-AMD running: yes
Sound Interface: sndio v: N/A running: no
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: Foxconn
driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 05:00.0 chip-ID: 168c:0034 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
Device-1: Foxconn / Hon Hai type: USB driver: btusb v: 0.8 bus-ID: 3-6:4
chip-ID: 0489:e076 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 3.38 TiB used: 1.15 TiB (33.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: Rocket 4.0 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: RKT401.3
temp: 44.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:4 model: PCIe SSD size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
type: SSD serial: <filter> rev: EHFM31.1 temp: 50.9 C scheme: MBR
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: A-Data model: SP550 size: 223.57 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD
serial: <filter> rev: 3B5a
ID-5: /dev/sdc maj-min: 8:32 vendor: Mushkin model: MKNSSDCR480GB-7-A
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: BBF0
Partition:
ID-1: / raw-size: 896.76 GiB size: 896.76 GiB (100.00%) used: 877.46 GiB
(97.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-fdeba41a-daf3-4497-ad26-81235b8d841f
ID-2: /boot raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 284.5 MiB
(95.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 896.76 GiB size: 896.76 GiB (100.00%) used: 877.46
GiB (97.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-fdeba41a-daf3-4497-ad26-81235b8d841f
ID-4: /var/log raw-size: 896.76 GiB size: 896.76 GiB (100.00%) used: 877.46
GiB (97.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-fdeba41a-daf3-4497-ad26-81235b8d841f
ID-5: /var/tmp raw-size: 896.76 GiB size: 896.76 GiB (100.00%) used: 877.46
GiB (97.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-fdeba41a-daf3-4497-ad26-81235b8d841f
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.27 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.45 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/dm-3 maj-min: 254:3
mapped: luks-317c8a85-28be-4c8e-b38d-98f1eb5cd257
Sensors:
System Temperatures: cpu: 51.2 C mobo: N/A gpu: amdgpu temp: 53.0 C
mem: 54.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
Processes: 411 Uptime: 7m wakeups: 0 Memory: 31.27 GiB used: 5.67 GiB
(18.1%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: pm: pacman pkgs: 1941
libs: 498 tools: octopi,paru pm: flatpak pkgs: 0 Shell: fish v: 3.5.1
default: Bash v: 5.1.16 running-in: yakuake inxi: 3.3.22
Garuda (2.6.8-1):
System install date:     2021-12-15
Last full system update: 2022-10-19
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Timeshift (maybe)
Failed units:            media-retronasShare.mount

Kernels are simply like your choice of footware. Use whatever kernel is most comfortable for you. If you are worried about getting hurt by hazards use a steel toed boot, (linux-hardened). If you want to look flash, and have the latest and greatest use the linux-mainline, (good choice for new hardware). Comfy old slippers (linux-lts). Choose whatever feels best on your system. There is no need to always run the Zen kernel. There are lots of kernels out there to fit everyone's needs.

5 Likes

Hi there!
I know this is quite a long shot, but by any chance SecureBoot might have decided to turn on after switching your CPU? Garuda is known for getting angry at secureboot!

I just checked, secureboot is set to otherOS in my bios (it doesn't have an option labeled disabled, only windows or otherOS) and shows up as disabled in the output of bootctl status

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.