this post was submitted on 12 Mar 2025
17 points (94.7% liked)

Linux

51586 readers
364 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
17
CPU errors? (feddit.nl)
submitted 12 hours ago* (last edited 4 hours ago) by lemmyvore@feddit.nl to c/linux@lemmy.ml
16 comments fedilink hide all child comments
 

I'm trying a new CPU in my PC (Ryzen 5500GT) and I'm seeing:

  • Sporadic kernel panics during boot.
  • Random .ko.zst module files (different one each boot) complaining that ZST decompression failed checksum.
  • Random .so's failing to find a symbol and causing programs to crash/fail to start.
  • Started a stress-ng sequential session at 5s per stressor and it hung up after a dozen stressors. Couldn't ctrl-c it and also ps didn't work anymore. 😅

Funny thing is, other than that the system runs fine (when it boots, that is).

Switched back to my old CPU (that's the only change in the machine) and all of these things stopped.

That CPU that's doing that is defective, correct? Just double-checking I'm not missing anything else.

I've reset BIOS between CPU swaps and left it at defaults. Could default settings cause a CPU to act like this?

Edit: cooling is good, all temps (chipset, CPU etc.) are in the 30's C in idle, CPU went up to 75C when stressed. Have a tower cooler (Scythe Kotetsu) with a 120mm fan.

I'm also adding some voltage readings I took from sensors while the problematic CPU was installed:

Vcore: 840mV
+3.3V: 3.31V
+12.0V: 12.10V
+5.0V: 5.01V
VSOC: 780mV
VDDP: 900mV
DRAM: 1.21V
3VSB: 3.29V
VBAT: 3.26V
top 16 comments
sorted by: hot top controversial new old
[–] just_another_person@lemmy.world 6 points 10 hours ago (1 children)
  1. Check if the CPU is overheating. You didn't mention anything about cooling.
  2. Are you sure your installed RAM is frequency compatible with the new CPU?
[–] Markaos@discuss.tchncs.de 6 points 9 hours ago (1 children)

I don't think overheating would cause random corruptions (it should throttle down when overheating, and then shut down if the temperature gets too high even when throttled, but there should never be an incorrect result of any computation), and surely the RAM will run at the standard 2133 speed on default settings - OP says they reset the BIOS settings to default between CPU swaps.

[–] lemmyvore@feddit.nl 3 points 4 hours ago

RAM is indeed at 2133 MHz and the cooling is great, got a tower cooler (Scythe Kotetsu mark II), idle temps are in the low 30's C, stress temp was 76C.

[–] catloaf@lemm.ee 4 points 10 hours ago (1 children)

It might be the CPU, but it might be something else. On the old CPU, update the OS, update the BIOS, and run fwupd or boot Windows temporarily to update all other firmware. Then run memtest and a cpu stress test to make sure you're not just triggering an existing hardware issue.

If that's all clean, put in the new CPU and run memtest and a cpu stress test to see where you get issues.

[–] lemmyvore@feddit.nl 3 points 4 hours ago (1 children)

Everything is up to date as far as I can tell, I did Windows too.

memtest ran fine for a couple of hours, CPU stress test hang up partway through though, while CPU temp was around 75C.

[–] FauxLiving@lemmy.world 5 points 3 hours ago (1 children)

75C is fine, the CPU will throttle in order to avoid max temps. This isn't something that should cause instability.

It's POSSIBLE that this is a bug that's fixed with a microcode update, see here for installing it: https://wiki.archlinux.org/title/Microcode

TL;DR:

  1. Install amd-ucode
  2. Edit /etc/mkinitcpio.conf, add microcode after autodetect
  3. sudo mkinitcpio -P
  4. reboot

If that doesn't fix it, and it crashes in Windows too, it may be a hardware problem. There isn't much you need to do in order to get a CPU working.

[–] lemmyvore@feddit.nl 2 points 1 hour ago* (last edited 1 hour ago) (1 children)

This sounds like my best shot, thank you.

I've installed the amd-ucode package. It already adds microcode to the HOOKS array in /etc/mkinitcpio.conf and runs mkinitcpio -P but I've moved microcode before autodetect so it bundles code for all CPUs not just for the current one (to have it ready when I swap) and re-ran mkinitcpio -P. Also had to re-run grub-mkconfig -o /boot/grub/grub.cfg.

I've seen the message "Early uncompressed CPIO image generation successful" pass by, and lsinitcpio --early /boot/initramfs-6.12-x86_64.img|grep micro shows kernel/x86/microcode/AuthenticAMD.bin, there's a /boot/amd-ucode.img, and an initrd parameter for it in grub.cfg. I've also confirmed that /usr/lib/firmware/amd-ucode/README lists an update for that new CPU (and for the current one, speaking of which).

Now from what I understand all I have to do is reboot and the early stage will apply the update?

Any idea what it looks like when it applies the microcode? Will it appear in dmesg after boot or is it something that happens too early in the boot process?

[–] FauxLiving@lemmy.world 2 points 49 minutes ago

Yup, just reboot to apply it.

It'll show up in dmesg: "microcode updated early to Rev. ###' etc

[–] sga@lemmings.world 3 points 11 hours ago (1 children)

can you give more details about your system, what kernel you are using what distro? also, have you tried testing a live boot usb to do testing, and also (I am presuming that you changed motherboard, and kept rest same) can you replace 1 part at a time and check.

Usually random breakages mean memory or power errors, and even different modules breaking can be caused by corrupt storage (maybe the readheads of hdd are broken, or if ssd, something something something, maybe broken/damged contacts). But you say going back to older cpu fixed this. Can you check what speed does your menory work at, sometimes, stable ram speeds depend on cpu, maybe you had it lower/higher for older cpu (usually lower than stable is not issue, higher is the issue), or maybe, your newer cpu is drawing more power, or you have some kind of faulty contact and some stray currents are developing on your motherboard. A fey more details would be really helpful

[–] lemmyvore@feddit.nl 1 points 4 hours ago

All hardware is the same, I'm trying to upgrade from a Ryzen 3100 so everything should be compatible. Both old and new CPU have a 65W TDP.

I'm on Manjaro, everything is up to date, kernel is 6.12.17.

Memory runs at 2133 MHz, same as for the other CPU. I usually don't tweak BIOS much if at all from the default settings, just change the boot drive and stuff like "don't show full logo at startup".

I've add some voltage readings in the post and answered some other posts here.

[–] KnightontheSun@lemmy.world 2 points 6 hours ago (1 children)

What motherboard? What cpu did you have? Is this new Ryzen 5600 on the hardware list for the motherboard? If so, are there any voltage, stepping or other settings (listed in the manual) required to make it run stably?

Make sure the new cpu is clean with no potential shorts from anything. Also ensure good heatsink contact. If you’ve done all the normal and necessary steps then yes it might be a bad cpu, but they aren’t frequent failure items in my experience. Disagreeable conditions for the cpu is more commonly the culprit. Engineering sample cpus are the most fickle, but even some normal batch cpus might sometimes require a bit more (or less) juice or a system tweak.

[–] lemmyvore@feddit.nl 2 points 4 hours ago

Motherboard is a Gigabyte B450 Aorus M. It's fully updated and support for this particular CPU is explicitly listed in a past revision of the mobo firmware.

Manual doesn't list any specific CPU settings but their website says stepping A0, and that's what the defaults were setting. Also I got "core speed: 400 MHz", "multiplier: x 4.0 (14-36)".

even some normal batch cpus might sometimes require a bit more (or less) juice or a system tweak

What does that involve? I wouldn't know where to begin changing voltages or other parameters. I suspect I shouldn't just faff about in the BIOS and hope for the best. :/

[–] BombOmOm@lemmy.world 2 points 11 hours ago (1 children)

Things to try:

  • Update your BIOS, this will likely solve the issue since things are working fine with your prior CPU.
  • If you are running an XMP/EXPO profile, turn it off, as it might be making your system unstable.
  • Memtest. Run it for at least a full cycle (which takes about an hour). If you see more than a single error, then there is something wrong with your RAM.
[–] lemmyvore@feddit.nl 2 points 4 hours ago

BIOS is up to date, CPU model explicitly listed as supported, memtest ran fine, not using XMP profiles.

[–] lemming741@lemmy.world 1 points 2 hours ago (1 children)

I had a 3700x that would lock up sometimes at light usage. Passed every stress test, and could idle for days. I swapped ram, psu, and mb with no effect. It's possible the microcode and firmware mentioned here could have fixed it but I got another CPU and all my problems went away. Worth the $200 for me.

[–] lemmyvore@feddit.nl 2 points 54 minutes ago

It's a pain in the butt to swap CPUs one more time but that may pale in comparison to trying to convince the shop that a core is bad and having intermittent faults. 🤪