Skip to main content ↑ ↓
Topic: Intel-microcode 01082018 WARNING  (Read 1322 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Intel-microcode 01082018 WARNING

I know this previous subject on the system list (Intel MEI)  is very related but not exactly.
https://forum.artixlinux.org/index.php/topic,359.0.html

Is everyone here with Intel hw aware that if you had the intel-microcode installed and updated and then rebooted, according to official Intel statements of last week you are screwed!

Not only the Intel patches do not protect you of anything but create even more problems with several reports of machines arbitrarily rebooting without warning.  I gathered some info yesterday on the subject and put an article together https://sysdfree.wordpress.com/173 but it is generally best to do your own research on the subject and decide.
Debian has already reverted back to the previous edition 11172018, but whoever had already updated the damage was done.

There are several threads here with advise to people with hw problems to install intel-ucode and tool, so I assume the bad news affects many.




Re: Intel-microcode 01082018 WARNING

Reply #1 –
Quote
We have received reports from a few customers of higher system reboots after applying firmware updates. Specifically, these systems are running Intel Broadwell and Haswell CPUs for both client and data center. We are working quickly with these customers to understand, diagnose and address this reboot issue. If this requires a revised firmware update from Intel, we will distribute that update through the normal channels.

https://newsroom.intel.com/news/intel-security-issue-update-addressing-reboot-issues/

Kaby lake here, latest microcode, no issues (but I've heard they are also affected, not just broadwell and haswell).

They're promising "true" hardware fixes in 2018.

I've had it with Intel.

Fortunately, PSU/case/cpu cooler/RAM/storage are reusable.

And of course, their stock prices are UP. Just because. :facepalm:

This was entirely unprofessional on their part, and they are trying to hide it with PR.