http://bugzilla.novell.com/show_bug.cgi?id=987358 http://bugzilla.novell.com/show_bug.cgi?id=987358#c2 --- Comment #2 from Robby Engelmann --- some more infos: I am using a crypt-lvm setup on skylake. Zaitor mentioned that he already updated two intel machines without issue. He did not use crypt-lvm setup on both. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=987358 http://bugzilla.novell.com/show_bug.cgi?id=987358#c4 --- Comment #4 from Cristian Rodríguez --- Well.. unless it is a problem in the kernel side that loads the microcrode..or a problem in dracut that creates a microcode blob that makes the kernel choke..there is nothing we can do about it other than reverting it. it is closed source.. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=987358 http://bugzilla.novell.com/show_bug.cgi?id=987358#c6 --- Comment #6 from Robby Engelmann --- I bought a Tuxedo InfinityBook v2 in April this year. Thus, I would think the BIOS is up-to-date. I do not know how to check this. Did anybody try to update it on an crypt-lvm setup machine? And will add the dracut output from the update here. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=987358 http://bugzilla.novell.com/show_bug.cgi?id=987358#c8 --- Comment #8 from Cristian Rodríguez --- (In reply to Robby Engelmann from comment #6)

I bought a Tuxedo InfinityBook v2 in April this year. Thus, I would think the BIOS is up-to-date. I do not know how to check this. Did anybody try to update it on an crypt-lvm setup machine? And will add the dracut output from the update here.

Tuxedo should supply firmware updates.. crypt-lvm is not involved in your issue..your system fails to load the initrd in the first place.. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=987358 http://bugzilla.novell.com/show_bug.cgi?id=987358#c10 --- Comment #10 from Robby Engelmann --- the BIOS is quite fresh: BIOS Information Vendor: American Megatrends Inc. Version: 5.11 Release Date: 04/08/2016 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=987358 Cristian Rodríguez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmarek@suse.com Flags| |needinfo?(mmarek@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=987358 Cristian Rodríguez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fenghua.yu@intel.com Flags| |needinfo?(fenghua.yu@intel. | |com) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=987358 http://bugzilla.novell.com/show_bug.cgi?id=987358#c15 --- Comment #15 from Robby Engelmann --- (In reply to Takashi Iwai from comment #13)

(In reply to Cristian Rodríguez from comment #12)

...

Hi Michal.. do you know how to debug a hang during the initrd loading or the early microcode stuff ?

Try to pass dis_ucode_ldr boot option. This will disable the early microcode loading.

If this helps, it implies that the ucode is the culprit. You can try to downgrade the ucode-intel package.

I updated to the snapshot containing the updated ucode-intel package --> boot hang I updated to the snapshot containing the updated ucode-intel package but this time updated all packages except for ucode-intel --> no boot hang --> thus, it should be clear that the ucode package was the culprit. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=987358 http://bugzilla.novell.com/show_bug.cgi?id=987358#c20 --- Comment #20 from Robby Engelmann --- works! [ 0.000000] microcode: microcode updated early to revision 0x9e, date = 2016-06-22 -- You are receiving this mail because: You are on the CC list for the bug.