this post was submitted on 23 Jul 2024
0 points (50.0% liked)

Technology

1345 readers
556 users here now

Which posts fit here?

Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.


Rules

1. English onlyTitle and associated content has to be in English.
2. Use original linkPost URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communicationAll communication has to be respectful of differing opinions, viewpoints, and experiences.
4. InclusivityEveryone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacksAny kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangentsStay on topic. Keep it relevant.
7. Instance rules may applyIf something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.


Companion communities

[email protected]
[email protected]


Icon attribution | Banner attribution

founded 11 months ago
MODERATORS
 

But microcode update can't fix CPUs that are already crashing or unstable.

top 1 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 3 months ago* (last edited 3 months ago)

First Ars article I’ve downvoted in a while. They’re not doing NEARLY as thorough of a job on this as L1 or GN.

There is a LOT more going on here than what Intel’s official line here implies, and the additional context makes this whole situation look like Intel isn’t being upfront and forthcoming with some pretty serious details on the failure. The way Intel is playing this is starting to look a lot like CYA, but this issue has been so bad that business partners who would normally remain silent are starting to talk to people like GN and L1 about lithography issues (supposedly fixed since then, but Intel has so far refused to specify date or serial ranges potentially affected, so who knows really) in addition to potential voltage issues. They’re only starting to release info on this now because these two channels are digging in WAY harder than I think Intel expected anyone to bother with.