I have a Ryzen 3 1300X at the moment and it’s always had this soft lock freezing bug on Linux. I used to dual-boot Windows on this machine and Windows never had the same problem, so I think it is an issue with the Linux kernel (I’ve also replaced nearly every bit of hardware that I originally built the PC with, except for the CPU and motherboard, so it probably is an issue the kernel has with my CPU, or possibly the motherboard firmware).

I’ve changed the kernel parameters as suggested by the Arch Wiki. The bug is pretty inconsistent about happening so only time will tell if this solves the issue. But if it doesn’t solve the issue, I’d honestly consider just getting a new CPU that doesn’t have this issue, as completely freezing up, unable to get to a tty or anything, and only being able to power off by physically holding down the power button, is a pretty major issue, even if it only happens sometimes.

So if I do get a new CPU, or maybe just for when I’m next buying a CPU for reasons unrelated to this bug (been considering an upgrade to something that’s better for compiling anyway), are there any good options out there? Intel is investing $25 billion into Israel and the BNC has called for “divestment and exclusion” from it (it’s not officially on the BDS consumer boycott list, but I’m still very much not comfortable buying from Intel). But the Arch Wiki article seems to suggest this bug is applicable to Ryzen CPUs in general, or at least it never specifies a particular model or range of models. So maybe I’m limited to non-Ryzen AMD CPUs?

I’m guessing this is one of the situations where two companies have a complete duopoly over the market and there isn’t an all-round good solution, but thought I’d ask in case anyone had some useful input.

  • catloaf@lemm.eeEnglish
    37·
    2 years ago

    Buy Intel used so that you’re not directly contributing?

    Other than that or AMD, your only other option is ARM.

  • bzLem0n@lemmy.ca
    13·
    2 years ago

    I have a system with a Ryzen 1700 with the same issue and have found the only reliable way to run it is by installing and enabling the disable-c6-systemd package from the AUR. The other fixes provided in the wiki article you linked are correct but aren’t sufficient on my system, the CPU keeps reenabling the C6 state on its own and the disable-c6-systemd package works to counter that. The reason it works on Windows is they’ve disabled the C6 state by default for the CPU.

    • Buffalox@lemmy.world
      6·
      2 years ago

      This is amazing to find out now after 7 years:) I actually adjusted voltage manually on my Ryzen R5 1600, and it became 100% reliable, apparently the fix you mention prevent voltage below 1v at idle. I wondered why my CPU wasn’t reliable unless I made manual OC with some voltage tweaks?

      I never looked it up, because my OC solved the issue, but I always thought it was a bit weird.

    • communism@lemmy.mlOP
      4·
      2 years ago

      Ah, thanks. I’m using runit not systemd (although this was happening on systemd when I was on systemd too) but I saw amd-disable-c6 in the AUR so I’ve installed that now, fingers crossed it works (the fixes in the Arch Wiki article haven’t fixed it for me, it just happened again rip)

      Edit: nvm, looks like that package is a systemd service

      • bzLem0n@lemmy.ca
        5·
        2 years ago

        The package is just a systemd unit to run the command python zenstates --c6-disable so if you install the zenstates-git package and get runit to run that command at startup it would be equivalent.

        • communism@lemmy.mlOP
          7·
          2 years ago

          Thank you!!

          Edit: Tried running that, I’m getting the error that /dev/cpu/0/msr doesn’t exist. dev/cpu doesn’t seem to exist at all on my machine. Hm

          Edit 2: You need to run sudo modprobe msr. All good now :)

    • merthyr1831@lemmy.world
      2·
      2 years ago

      A few more years until RISC-V is at 1st-gen ryzen levels (though it looks like RISC-V is accelerating every day)

  • bruhduh@lemmy.world
    6·
    2 years ago

    My Ryzen 5700u work great with Debian, so as others said, consider upgrade CPU on your am4 motherboard, better buy apu since it always feels good to have backup gpu in your system in case main gpu breaks

    • Norah (pup/it/she)@lemmy.blahaj.zoneEnglish
      3·
      2 years ago

      I don’t think getting an APU ‘just in case’ is a good idea. It limits your turbo frequency and halves your L3 cache compared to the equivalent CPU variants. It also limits you to PCIe 3.0 only. Some AM4 boards have a single 4.0 x16 slot for graphics cards, so getting an APU could directly affect the graphics performance from a discrete GPU. OP should get the chip that is more suited to their typical use case.

    • communism@lemmy.mlOP
      5·
      2 years ago

      Ah. I’m getting this answer a lot actually. I might try a newer Ryzen then if a lot of people are saying the newer Ryzens work

    • communism@lemmy.mlOP
      1·
      2 years ago

      Not sure where they’re declaring it happens for “all Ryzen” from.

      I’ve not see anyone claim it happens on “all Ryzen”, just that the Arch Wiki article doesn’t specify a particular range or model

  • HumanPerson@sh.itjust.worksEnglish
    4·
    2 years ago

    As I understand, early ryzen processors are generally more buggy. I run 5800x on my desktop and a 5600(x?) in my server. You could try a newer ryzen and see if it works. I would recommend shopping around for a decent warranty.

    • communism@lemmy.mlOP
      1·
      2 years ago

      That’s good to hear that you’re not having problems on newer Ryzen. Although not sure if I want to risk buying a new Ryzen CPU if there’s a chance I could have the same problem

  • MrAlternateTape@lemm.ee
    3·
    2 years ago

    While it probably isn’t the issue for you, I have once been chasing a hard freeze that was caused by some APM setting in the BIOS. If you are on AMD right now you could check it.

    It was very weird, setting it to automatic would cause random freezes. Setting it to on or off would both work just fine. Somehow the automatic setting gave me issues.

    Just a random thing for you to check I guess.

  • Buffalox@lemmy.world
    3·
    2 years ago

    I had a similar problem with a Ryzen 5 1600, at first it worked flawlessly when I did a manual OC, then when I made a reset, I didn’t care to OC again, and it began to occasionally freeze, usually when idle. When I made my manual OC again including upping voltages a bit for CPU and RAM it worked flawlessly again???

    Weird since motherboard defaults aught to be stable IMO, but apparently they aren’t always.

    I’ve been using this CPU for 7 years now, and it still runs like a champ, as long as I don’t use the motherboard defaults. I can’t remember last time it crashed or froze.

    EDIT:

    I just found out the package “disable-c6-systemd” mentioned in your link, is exactly to prevent voltage drop below 1v at idle, which sounds exactly like the bug I had. which is funny to learn 7 years later. ;)

  • png@discuss.tchncs.de
    3·
    2 years ago

    Get another AMD chip, you’ve just been unlucky. I’ve had AMD running Linux for 5 years with no issues.

  • NorthCountryHermit@lemm.eeEnglish
    53·
    2 years ago

    Flapping about, feeling morally superior… did you even try to search for an answer or did you just want to virtue signal? Take a look at RIsc, or Arm… or w/e the Chinese just released.

  • TCB13@lemmy.worldEnglish
    31·
    2 years ago

    I’ve no ideia what you’re rambling about. I can attest that the Ryzen 5 1600 and the Ryzen 5 2600 that aren’t even new CPUs run perfectly fine with Debian.