100%. Whatever Intel does at this point, I don’t trust it to be a fix so much as a mitigation or attempt to delay the inevitable until a few years after the warranty period.
If it’s possible for people to return their 13th/14th gen processor and trade up for a 12th gen, that would be the safest solution.
Moore’s Law is Dead shared an interesting video yesterday about these chips. Supposedly, leaks from his sources at Intel say that high voltages being pushed through the ring bus cause degradation. The leaks claim it shares the same power rail as the P and E cores, meaning it’s influenced by the voltage requested by the cores.
For context, the ring bus is responsible for communication between cores, peripherals, and the platform. This includes memory accesses, which means that if the ring bus fails and does something incorrectly, it could appear normal but result in errors far down the line.
Going beyond the video specifically, and considering what others have suggested as workarounds, it seems like ring bus degradation might be a decent candidate for the actual root cause of these issues.
Some observations around chips degrading were:
Some of the suggestions to work around the issue were:
All of those can be related to stress being put on the ring bus:
I’m not claiming anything definitive, but I think my money is on this one.
They certainly tried with Secure Boot. Thank Stallman that UEFI is a somewhat-open architecture.
Smoldering at best, sadly. It will take a lot more before Reddit goes and Digg V3’s itself.
Every bit counts at least.
Probably fear, then subsequently followed by their brains next to you on said wall. Whichever government paid for a multi-year campaign to backdoor enterprise Linux distributions is not going to be happy about this failure.
The fact that they actually have dynarmic and sirit sources puts this one a step ahead of the failed-and-now-closed Nuzu fork.
Nuzu also shut down within a day.
Voluntary from the perspective of GitHub. If it was through a DMCA request, all the forks would be gone with it.
I wish I were joking, but it boils down to “condemn piracy, tell everyone emulation is legal, and keep the code open-source.”
Source, as stated on the project subreddit. In the same post, he also disclosed his country of residence.
This fork doesn’t even have the code for the dynarmic submodule under the externals/dynarmic directory. MerryMage/MerryHime took that down with Yuzu, and it’s a core part of the JIT recompiler.
Not to mention, the commit history was wiped clean while a new Patreon was created before even touching a line of C++ code (and subsequently realizing it’s missing most of the dependencies).
The release downloads work, but I don’t expect a long future for that project. The creator publicly posted his country of residence on Reddit, and doesn’t have much of a plan to avoid a lawsuit other than “we’ll condemn piracy wherever we can.”
On top of that, it has a brand-new Patreon and is missing the source code for core parts of the emulator.
The repository removal was voluntary and done by the Yuzu team. GitHub doesn’t have to do anything and won’t do anything. Even when they receive a DMCA takedown, they only block forks made through GitHub’s “fork” button.
The system is absolutely bullshit. If this makes it into a courtroom, the odds will likely be even further stacked against Yuzu. The chance of getting a judge that goes out of his/her way to understand the technical arguments is extremely low, and it’s a lot easier to argue that unauthorized decryption is bypassing something than it is to argue that software needing to do it to work isn’t primarily designed to do it.
Unless the EFF steps in and bankrolls Yuzu, the most realistic case here is that they settle out of court and Nintendo gets exactly what they want.
If Nintendo can prove that the primary purpose of Yuzu is to circumvent Nintendo’s encryption, there is a very real and very scary chance they could win the lawsuit.
17 USC §1201 (a)(2)
No person shall manufacture, import, offer to the public, provide, or otherwise traffic in any technology, product, service, device, component, or part thereof, that—
(A) is primarily designed or produced for the purpose of circumventing a technological measure that effectively controls access to a work protected under this title;
(B) has only limited commercially significant purpose or use other than to circumvent a technological measure that effectively controls access to a work protected under this title; or
© is marketed by that person or another acting in concert with that person with that person’s knowledge for use in circumventing a technological measure that effectively controls access to a work protected under this title.
Dungeons & Bad Dragons
We really don’t need more than #3 for a reason to stay far away from Telegram. Security through obscurity is not security, and neither is rolling your own crypto.