https://bugzilla.kernel.org/show_bug.cgi?id=117301 Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmh@xxxxxxxxxx --- Comment #2 from Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> --- You have a mixed-stepping hardware configuration: signatures 0x6f7 -- stepping B3 and 0x6fb -- stepping G0. I was not even aware this was a supported configuration, although re-reading the exact language in the data sheet for the Xeon 5300, it *is* supported. However, a Google search found an Intel Product Change Notification, numbers PCN 107893-00 and PCN 107467-00, which are *quite clear* that it is indeed supported, *but that it requires an updated BIOS and microcode on both processors*. It is not just the microcode, the BIOS has to set some MSR registers on the processors to enable cross-stepping compatibility (likely it dumbs down the 0x6fb one). So, there you have it: the motherboard BIOS did not initialize the microcode of the 0x6fb processor (it is at revision 0), therefore it seems safe to assume it does not support your hardware configuration. Update that BIOS. After you do that, you also need to ensure the Linux early microcode update will also attempt to update that second processor: from the logs, it is being updated too late (by the late microcode update). Ensure both microcode updates are present in the early initramfs created by dracut... if it still doesn't work, we have a bug in the Linux early microcode loader. Now, I have to fix some userspace that mistakenly assumes such mixed-stepping configurations are illegal... (iucode-tool, I don't think it is used by Fedora, RHEL and CentOS, though). -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
