• exanime@lemmy.world
    link
    fedilink
    arrow-up
    17
    ·
    edit-2
    3 months ago

    But isn’t the fix basically under clocking those CPU?

    Meaning the “solution” (not even out yet) is crippling those units before the flaw cripples them?

    • Kazumara@discuss.tchncs.de
      link
      fedilink
      arrow-up
      10
      ·
      edit-2
      3 months ago

      They said the cause was a bug in the microcode making the CPU request unsafe voltages:

      Our analysis of returned processors confirms that the elevated operating voltage is stemming from a microcode algorithm resulting in incorrect voltage requests to the processor.

      If the buggy behaviour of the voltage contributed to higher boosts, then the fix will cost some performance. But if the clocks were steered separately from power, and the boost clock is still achieved without the overly high voltage, then it might be performance neutral.

      I think we will know for sure soon, multiple reviewers announced they were planning to test the impact.

    • w2tpmf@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      3 months ago

      That was the first “Intel Baseline Profile” they rolled out to mobo manufacturers earlier in the year. They’ve roll out a new fix now.

        • w2tpmf@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          3 months ago

          I have a i7-13700k that’s been sitting in the box since I got a deal on it last month. I was pondering returning it and spending the extra couple hundred to get an AMD setup.

          I’ve been following all this then checked on the Asus site for my board and saw the BIOS updates…

          Updated with microcode 0x125 to ensure eTVB operates within Intel specificatIons…

          And this week there’s a beta release…

          The new BIOS includes Intel microcode 0x129…