Microcode for 206C2 Westmere EP is missing

Same for Lynnfield Xeon (CPUID 106E5).

Same for Ivy Bridge E (CPUID 306e4)

For 0x206c2:
Refer to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907402

0x206c2 is missing *from the Debian and Ubuntu packages* on purpose, but we could ship it if Intel explicitly tells us it is not going to permanently disable a box that has a very old BIOS with the blacklisted SINIT ACM for Intel TXT AND which happens to have Intel-TXT-based secure boot enabled in BIOS.

For 0x106e5, 0x306e4:
They are present in the intel-microcode packages in Debian, so I will leave the answer to the Ubuntu maintainer. Are you sure they are really missing from /lib/firmware/intel-ucode?

This will check if the microcodes are in the package (run it with the package installed and no extra manually-added microcodes in /lib/firmware/intel-ucode or /usr/share/misc/intel-microcode*)

iucode_tool -q -l -s 0x106e5 -s 0x306e4 /lib/firmware/intel-ucode

" reports they exist, then your issue is that they're not being installed to the initramfs.

Confirmed information from microcode team:

206F2 – Westmere-EX Rev 0x3B shows as OK for OS load. The prior one marked as Production was 0x39 and mark as NOT_FOR_OS.

206C2 – Westmere-EP Rev 0x1F and 0x1E shows as OK for OS load and the prior production revision 0x1D is marked as NOT_FOR_OS.

On Tue, 09 Oct 2018, <email address hidden> wrote:
> Confirmed information from microcode team:
>
> 206F2 – Westmere-EX Rev 0x3B shows as OK for OS load. The prior one marked as Production was 0x39 and mark as NOT_FOR_OS.
> 206C2 – Westmere-EP Rev 0x1F and 0x1E shows as OK for OS load and the prior production revision 0x1D is marked as NOT_FOR_OS.

Thank you.

Since you report that the Intel microcode team explicitly told us to
ship these two microcode updates to users, I will update the Debian
package to do so.

Ubuntu will either pick it up from there, or do the same.

--
  Henrique Holschuh

I have just uploaded intel-microcode 3.20180807a.2. to Debian, which does distribute 0x206c2.

All other microcodes cited on this bug report have been properly distributed by Debian, and presumably by Ubuntu. As far as I am concerned, this bug is either fixed-upstream (in Debian), or more-information-needed because @jan-kellermann has decided to not comment further.

As far as I am concerned, unless new information is posted soon, this bug report can be closed as soon as Ubuntu pulls in 3.20180807a.2 from Debian.

Sorry, I read this as information and not as a question :)

You are right: the other microcodes were includes, we had a problem with loading them in grub.

Thank you for all!

This bug was fixed in the package intel-microcode - 3.20180807a.2

---------------
intel-microcode (3.20180807a.2) unstable; urgency=medium

  * Makefile: unblacklist 0x206c2 (Westmere EP)
    According to <email address hidden>, on message to LP#1795594
    on 2018-10-09, we can ship 0x206c2 updates without restrictions.
    Also, there are no reports in the field about this update causing
    issues (closes: #907402) (LP: #1795594)

 -- Henrique de Moraes Holschuh <email address hidden> Tue, 23 Oct 2018 19:52:40 -0300