| Here's a fix which works here - I'd appreciate it if you ran it and | checked the microcode was applied correctly, i.e.: | | $ dmesg | grep -i microcode | | before and after the patch. Please paste that output in a mail too. Hi Borislav, Sorry it's taken me so long. I've been having issues. I couldn't recreate that first boot failure, even using .config.old, and even after removing (rm -fR) my linux.git and untarring it from the original tarball, doing a make clean, etc. The output before and after your new patch are the same (except for the times): # dmesg | grep -i microcode [ 5.291679] microcode: microcode updated early to new patch_level=0x010000d9 [ 5.298761] microcode: CPU0: patch_level=0x010000d9 [ 5.303648] microcode: CPU1: patch_level=0x010000d9 [ 5.308529] microcode: CPU2: patch_level=0x010000d9 [ 5.313414] microcode: CPU3: patch_level=0x010000d9 [ 5.360834] microcode: CPU4: patch_level=0x010000d9 [ 5.365719] microcode: CPU5: patch_level=0x010000d9 [ 5.370602] microcode: CPU6: patch_level=0x010000d9 [ 5.375486] microcode: CPU7: patch_level=0x010000d9 [ 5.380372] microcode: CPU8: patch_level=0x010000d9 [ 5.385256] microcode: CPU9: patch_level=0x010000d9 [ 5.390142] microcode: CPU10: patch_level=0x010000d9 [ 5.395102] microcode: CPU11: patch_level=0x010000d9 [ 5.437813] microcode: CPU12: patch_level=0x010000d9 [ 5.442785] microcode: CPU13: patch_level=0x010000d9 [ 5.447755] microcode: CPU14: patch_level=0x010000d9 [ 5.452724] microcode: CPU15: patch_level=0x010000d9 [ 5.457756] microcode: Microcode Update Driver: v2.01 <tigran@xxxxxxxxxxxxxxxxxxxx>, Peter Oruba # uname -a Linux intec2 4.9.0-rc2+ #2 SMP Thu Oct 27 14:29:32 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Regards, Bob Peterson -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>