Technology

59405 readers

2546 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

Intel chip bug FAQ: Which PCs are affected, how to get the patch, and everything else you need to know (www.zdnet.com)

submitted 2 months ago by [email protected] to c/[email protected]

15 comments fedilink hide all child comments

top 15 comments

sorted by: hot top controversial new old

[–] [email protected] 12 points 2 months ago* (last edited 2 months ago) (1 children)

And here I thought, it would be good to go for Intel. Recently got a new PC with 14600KF. However, I have not had any issues with performance besides Deathloop (Launches, black screen and then dissapears).

EDIT: So I guess, I'm forced to wait until my motherboard developer/ company (MSI) announces that their users can update their BIOS manually? I'm curious whether, I'm actually affected by this or not. Though I guess, never gonna go Intel again. Next new PC will be having AMD (unless AMD makes such a mess as well, then it does not matter).

[–] [email protected] -4 points 2 months ago* (last edited 2 months ago) (4 children)

e.g. https://www.yahoo.com/tech/ryzen-3000-fix-sinkclose-vulnerability-183025768.html AMD has these sorts of flaws too, I don't know enough to tell if AMD is significantly better at this when deciding to buy

[–] [email protected] 10 points 2 months ago

That exploit required kernel access to begin with, which at that point, you have much bigger problems.

[–] [email protected] 13 points 2 months ago

So far the AMD security flaws aren't causing physical CPU damage, so Intel definitely wins the screw up award.

[–] [email protected] 22 points 2 months ago

That AMD security vulnerability doesn't physically damage the CPU while this Intel flaw does. Thats a drastic difference so the two are not the same

[–] [email protected] 6 points 2 months ago* (last edited 2 months ago)

Unfortunately, this problem is larger than a micro-code update. The main issue the user is likely referring to is Intel shipping defective product (oxidation issues), denying warranty claims for said defective product, then staying quiet when it's proven they have been shipping defective product. Intel could have owned up to the issue and proactively recalled defective units, but, they didn't do the honorable thing, not even close.

[–] [email protected] 21 points 2 months ago (4 children)

I thought they had corrosion issues, how do you patch that?

[–] [email protected] 16 points 2 months ago (1 children)

You can't fix damage that has already happened, but you can stop more damage by limiting voltage as I understand it.

[–] [email protected] 7 points 2 months ago (3 children)

but how can the chips reach the advertised performance while being undervolted? especially damaged chips.

[–] [email protected] 6 points 2 months ago

They can't.

[–] [email protected] 10 points 2 months ago* (last edited 2 months ago)

It's like spectre and meltdown you also lost the advertised performance. Less performance is better than a gaping security hole or a broken chip.

[–] [email protected] 5 points 2 months ago* (last edited 2 months ago)

I would expect this patch to come with a negative performance impact.

[–] [email protected] 5 points 2 months ago

As I understand it the corrosion is provoked by the chip's operation, the patch reduces the voltage load which makes the corrosion less likely to happen or to advance less quickly.

[–] [email protected] 4 points 2 months ago

Warranty replacement.

[–] [email protected] 13 points 2 months ago

🩹