06-ba-08 changed but not mentioned in the microcode-20240910 release notes
#83
Comments
|
0x000b06a8 was updated to the same microcode revision as the other steppings (0x000b06a2, 0x0000b06a3) were, so it looks like a simple omission from the release notes. Still, it would be nice to know for sure whether this update was intended or not [for this release]. |
|
Yes, you are correct. The MCU was updated for 06-ba-08 and is missing from the releasenotes.md file. |
|
Just to check, are you asking about 06-ba-08 because somebody has a processor with this CPUID or because it was included in the updated files? I went back and verified, 06-ba-08 is not yet a production product and so we don't need to support this family-model-stepping yet. |
|
Just because it was included in the updated files. |
|
This signature is an extended signature in a single microcode data file that covers sigs 0x000b06a2, 0x000b06a3 as well. It doesn't even make sense to not distribute it. Also, now that I did a search for it, we've been distributing this one since 20240312 in Debian (and so does everyone else)... it is on our automated changelogs generated using iucode_tool. |
This microcode file was first appeared as part of microcode-20240312,
was present in the following releases up to microcode-20241112,
and was removed in microcode-20250211. While [1] mentions
that there are no products in production that would use that microcode,
it does not warrant creation of discrepancy between the release notes
and the actually shipped contents; moreover, presence of 60BA8 CPUID
in [2] hints at its possible availability, after all.
NB: This CPUID can still be updated with the latest 06-ba-0* microcode
even despite removal of the microcode file, as it shares the microcode
data with 06-ba-02 and 06-ba-03 microcode files, that still contain
it in the extended signature:
% iucode_tool -L microcode-20250211/intel-ucode/06-ba-02
microcode bundle 1: microcode-20250211/intel-ucode/06-ba-02
001/001: sig 0x000b06a2, pf_mask 0xe0, 2024-07-31, rev 0x4124, size 220160
sig 0x000b06a2, pf_mask 0xe0, 2024-07-31, rev 0x4124
sig 0x000b06a3, pf_mask 0xe0, 2024-07-31, rev 0x4124
sig 0x000b06a8, pf_mask 0xe0, 2024-07-31, rev 0x4124
[1] intel#83 (comment)
[2] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01139.html
* releasenote.md (microcode-20240312): Mention addition of the microcode
at revision 0x4121.
(microcode-20240910): Mention an update to revision 0x4122.
(microcode-20241112)
Signed-off-by: Eugene Syromiatnikov <[email protected]>
This microcode file was first appeared as part of microcode-20240312,
was present in the following releases up to microcode-20241112,
and was removed in microcode-20250211. While [1] mentions
that there are no products in production that would use that microcode,
it does not warrant creation of discrepancy between the release notes
and the actually shipped contents; moreover, presence of 60BA8 CPUID
in [2] hints at its possible availability, after all.
NB: This CPUID can still be updated with the latest 06-ba-0* microcode
even despite removal of the microcode file, as it shares the microcode
data with 06-ba-02 and 06-ba-03 microcode files, that still contain
it in the extended signature:
% iucode_tool -L microcode-20250211/intel-ucode/06-ba-02
microcode bundle 1: microcode-20250211/intel-ucode/06-ba-02
001/001: sig 0x000b06a2, pf_mask 0xe0, 2024-07-31, rev 0x4124, size 220160
sig 0x000b06a2, pf_mask 0xe0, 2024-07-31, rev 0x4124
sig 0x000b06a3, pf_mask 0xe0, 2024-07-31, rev 0x4124
sig 0x000b06a8, pf_mask 0xe0, 2024-07-31, rev 0x4124
[1] intel#83 (comment)
[2] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01139.html
* releasenote.md (microcode-20240312): Mention addition of the microcode
at revision 0x4121.
(microcode-20240910): Mention an update to revision 0x4122.
(microcode-20241112)
Signed-off-by: Eugene Syromiatnikov <[email protected]>
The commit shows the file was modified.
The text was updated successfully, but these errors were encountered: