this post was submitted on 09 Aug 2024
665 points (98.3% liked)

Memes

51577 readers
1286 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 6 years ago
MODERATORS
gary_host_laptop@lemmy.ml
sexy_peach@feddit.de
cyclohexane@lemmy.ml
cypherpunks@lemmy.ml
665
Amd fan (lemmy.world)
submitted 11 months ago by Varven@lemmy.world to c/memes@lemmy.ml
112 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] w2tpmf@lemmy.world 14 points 11 months ago (2 children)

This keeps getting slightly misrepresented.

There is no fix for CPUs that are already damaged.

There is a fix now to prevent it from happening to a good CPU.

[–] exanime@lemmy.world 16 points 11 months ago* (last edited 11 months ago) (3 children)

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 11 points 11 months ago* (last edited 11 months ago) (1 children)

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 the voltage, 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.

[–] exanime@lemmy.world 1 points 11 months ago

Thanks for the clarification

[–] w2tpmf@lemmy.world 7 points 11 months ago (1 children)

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.

[–] Retrograde@lemmy.world 1 points 11 months ago

As an i9-13900k owner, thanks. My chip has been great so far, better update when I get home

[–] msage@programming.dev 3 points 11 months ago

Remember Spectre? When they recommended disabling hyperthreading?

[–] M0oP0o@mander.xyz 1 points 11 months ago (1 children)

Not out yet. But you can manually set your clocks and disable boost.

[–] Kazumara@discuss.tchncs.de 4 points 11 months ago (1 children)

Not out yet.

Actually the 0x129 microcode was released yesterday, now it depends on which motherboard you have and how quickly they release a bios that packages it. According to Anandtech Asus and MSI did already release before Intel made the announcement. I see some for Gigabyte and Asrock too.

https://community.intel.com/t5/Processors/Microcode-0x129-Update-for-Intel-Core-13th-and-14th-Gen-Desktop/m-p/1622129/highlight/true#M76014

[–] M0oP0o@mander.xyz 1 points 11 months ago (1 children)

So, not out yet. At least not fully.

[–] Kazumara@discuss.tchncs.de 3 points 11 months ago

If you prefer being right, rather than just accepting the extra information, then sure let's go with that.