Linux

53576 readers

1057 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

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

d3Xt3r@lemmy.nz

CPU errors? (feddit.nl)

submitted 1 month ago* (last edited 1 month ago) by lemmyvore@feddit.nl to c/linux@lemmy.ml

19 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

you are viewing a single comment's thread
view the rest of the comments

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

No, I would search for your motherboard model and forums to see what situations might match yours so that you might glean something useful as far as settings go. A quick check revealed nothing useful that stands out to me. Resetting all electrical connections was the lone useful tip. (The reddit link blocked me, lol. Fine) Perhaps more detailed (or different) search terms would produce better results.

I think you've taken the right steps to this point. Another CPU to test with would prove useful (though your original should suffice). Or another board to test this CPU in. Perhaps the shop you procured this one from has one or the other? Otherwise, I would pursue replacement.

[–] lemmyvore@feddit.nl 3 points 1 month ago

Honestly I'll just send it back at this point. I have kernel panics that point to at least two of the cores being bad. Which would explain the sporadic nature of the errors. Also why memcheck ran fine because it only uses the first core by default. Too bad I haven't thought about it when running memtest because it lets you select cores explicitly.