processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz I updated today, from sys-apps/microcode-data-20140624. After a reboot, my system hung while booting in "waiting for events to be processed". I used systemrescuecd to downgrade the microcode-data, and confirmed I could boot again. After this, I attempted to figure out my issue. I can see multiple things during boot in my log like: Apr 13 17:43:49 XXX kernel: traps: rpcbind[2607] trap invalid opcode ip:7f4471452c52 sp:7fff09a7f108 error:0 in libpthread-2.20.so[7f4471447000+16000] Apr 13 17:45:43 XXX kernel: traps: ntpd[2541] trap invalid opcode ip:7f1301e5195a sp:7ffc57d18b08 error:0 in libpthread-2.20.so[7f1301e46000+16000] Apr 13 17:46:25 XXX kernel: traps: pool[27433] trap invalid opcode ip:7f109d28d95a sp:7f109b89c988 error:0 in libpthread-2.20.so[7f109d282000+16000] Apr 13 17:46:25 XXX kernel: traps: gvfs-udisks2-vo[9508] trap invalid opcode ip:7f41a8ea495a sp:7ffe558a54a8 error:0 in libpthread-2.20.so[7f41a8e99000+16000] I noted that my CONFIG_MICROCODE=m, so I switched it to built-in, and enabled CONFIG_MICROCODE_EARLY=y. This time booting didn't hang "waiting for events to be processed", but crashed later on. I entered interactive mode, and it seems that consolekit is crashing with an invalid opcode as above. This caused my KDM to be unusable and appear hung. I then added the option to dracut --early-microcode, and this seems to have made the issue go away. I'm not sure what is the cause, or if this is a proper solution. I am merely providing information at the moment. Reproducible: Always
same here: Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz Stepping: 3 downgrade to =sys-apps/microcode-data-20140430 fixes it.
Same udev hang/opcode faults here on another Haswell: vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz stepping : 3 Switching the kernel's microcode from module to compile resolved the issue. No such issues encountered on an Ivy Bridge-E i7-4960X. I remember having such a problem with udev/microcode a few years ago which magically went away after some time.
*** This bug has been marked as a duplicate of bug 528712 ***
