Recently a serious bug has appeared. This bug affects users who have the latest Intel processors, Intel Skylake and Kaby Lake platform processors. Platforms that could cause us to lose data and even cause the operating system to behave abnormally and unpredictably.
The first to notice this serious bug have been the Debian developers, which have alerted us to the problem and have indicated a possible solution to this problem. However, this problem affects all operating systems, that is, it does not matter what platform we use because it will affect us if we have these processors. From Debian it is recommended or either disable HyperThreading or update the processor microcode. Debian has already released a processor microcode update for both Debian Jessie and the brand new Debian Stretch. But despite this there are still distributions and users who have not updated or will not update their distribution, so it is recommended to go to BIOS and disable HyperThreading. The problem that the Debian developers comment on lies in the HyperThreading of the new Intel processors, so by disabling it, we momentarily close the problem, but it is still there.
For its part, Intel has not commented on this bug or on how to solve the problem that the Debian guys report, but just as Intel is silent, other companies and developers also do. Apparently this bug has gone unnoticed by everyone. And this is serious because according to Debian, This bug is responsible for error messages such as corrupted data, data loss, etc.. Critical errors for users of servers and other computers using these Intel processors.
In any case, whether or not we have the updated microcode, it is best to disable HyperThreading, at least until Intel, the owner of the platform, decides on it. At least our team will be safe, don't you think?
The wording is very loose. Very lazy.
«… They have alerted about the problem and have indicated a possible solution to this problem. However, this problem affects… ». Correct that.
And where are the sources?
How sad it is to read comments like those of @RREDesigns that do not take into account dedication and effort.
How simple it is to criticize without contributing anything, unless @RREDesigns is willing to make an article to publish in linuxadictos
According to rolo
Lie, it affects ALL hyperthreading. I have an old test PC, a 3.04 GHz PIV mono with HT. The Win10 pulls it without problems and with the HT activated in linux it dies with a sad Mint.