Created attachment 356624 [details] The portion of the panic message that is visible on the screen The 3.10.7* series has a early boot panic for us. We are booting with a dracut initramfs, with a nfs root. Attached is a screenshot of the (end of) the panic message.
this is due to invpcid that exists on haswell only and should not be used anywhere else. what is the host cpu exactly? can you also capture the boot log perhaps via serial or netconsole?
the latest PaX patch has a fix for this (presumably ;), can you test it?
still an issue?
This seems to be fixed in 3.10.10