Linux Fixes Hosts Randomly Rebooting During Virtualization With Ryzen 7000/8000 CPUs

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Espionage724
    Senior Member
    • Sep 2024
    • 319

    #31
    Originally posted by intelfx View Post

    Nobody pays me to counter every piece of bullshit I see on the Internet.
    Fair enough, but it seems counter-productive to try to call out trolling without contributing something. I'm looking for discussion, what exactly are you doing?

    Comment

    • WannaBeOCer
      Senior Member
      • Jun 2020
      • 301

      #32
      Originally posted by caligula View Post

      At least many models of Ryzen series have been very competitive products. Before Ryzen AMD had only shit hardware. Intel has f*cked the asses of their buyers several times without using lube. Two whole generations of recent chips are flawed and will eventually break down. Lots of unimpressive products. Totally f*cked up energy consumption for some generations of i7 CPUs. Also most of the 3rd to 7th generation models were totally unimpressive in terms of performance. 2600/2700k was good, the next good model was 8700k. Most users were also affected by SPECTRE/MELTDOWN. So much performance lost due to incompetence.
      Two generations aren't flawed, it was a microcode issue. Unlike AMD who's microcode instantly fried the 7000X3D chips.



      Intel slow roasted them. Making it difficult to diagnose the issue since they died much later than at launch. Having to go through a RMA does suck but hopefully they update their bios prior to installing their replacement.

      I agree their architectures are inefficient. What pushed me away from buying AMD is the USB issue that still plagues many AM4 users. I went with the 12700K instead of the 5800X3D and since I game at 4K the CPU performance doesn't matter much unless playing a MMO.

      Comment

      • Espionage724
        Senior Member
        • Sep 2024
        • 319

        #33
        Originally posted by WannaBeOCer View Post
        ...
        I agree their architectures are inefficient. What pushed me away from buying AMD is the USB issue that still plagues many AM4 users.
        That bit me a bit with a Rift CV1 and X470 (on rear USB I couldn't push 3 sensors nor even just the HMD and luckily had a separate ASRock controller to push something to); a lower-spec'd Intel laptop handled the Rift with 3 sensors and random $10 eBay USB powered hub more stably surprisingly

        Comment

        • intelfx
          Senior Member
          • Jun 2018
          • 1083

          #34
          Originally posted by WannaBeOCer View Post
          Two generations aren't flawed, it was a microcode issue​
          Incorrect. It was a combination of a fabrication issue and silicon design issue(s) which Intel tried (and failed) to damage-control by rolling out a series of performance-reducing microcode patches.

          Comment

          • ssokolow
            Senior Member
            • Nov 2013
            • 5060

            #35
            Originally posted by intelfx View Post

            Incorrect. It was a combination of a fabrication issue and silicon design issue(s) which Intel tried (and failed) to damage-control by rolling out a series of performance-reducing microcode patches.
            *nod* See this video. The problem still occurred in datacenter machines where the server chipset didn't allow fancy tweaks and the used (default) configuration did everything but underclock the chips to prioritize reliability over performance.

            Comment

            • WannaBeOCer
              Senior Member
              • Jun 2020
              • 301

              #36
              Originally posted by intelfx View Post

              Incorrect. It was a combination of a fabrication issue and silicon design issue(s) which Intel tried (and failed) to damage-control by rolling out a series of performance-reducing microcode patches.
              There was a batch of contaminated wafers that are flawed. The majority of the issues is due to the microcode slowly roasting Intel's CPUs. Again it's the same issue as AMD's 7000X3D chips but more difficult to diagnose.

              Comment

              Working...
              X