https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c1 James Moe changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jimoe@sohnen-moe.com --- Comment #1 from James Moe 2012-10-30 17:46:28 UTC --- I have a similar issue. Hardware: AMD Athlon II x4 (635), 4GB RAM, Asus m3a78-em motherboard So far two systems (of 5) have shown the tendency to freeze during boot. The freeze occurs immediately after loading the microcode. The chance of a freeze is about 50%. Oct 28 19:47:08 linux kernel: [ 2.268561] [drm] Loading RS780 Microcode ... bunch o' stuff ... Oct 28 19:47:08 linux kernel: [ 4.342778] device fsid 0617578a-edca-4e3b-9100-729ae05c9057 devid 1 transid 57 /dev/sdc7 Oct 28 19:47:08 linux kernel: [ 4.343493] btrfs: disk space caching is enabled Oct 28 19:47:08 linux kernel: [ 7.348880] microcode: CPU0: patch_level=0x00000000 Oct 28 19:47:08 linux kernel: [ 8.280828] btrfs: disk space caching is enabled Oct 28 19:47:08 linux kernel: [ 8.330539] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found Oct 28 19:47:08 linux kernel: [ 8.330541] EDD information not available. Oct 28 19:47:08 linux kernel: [ 8.959184] microcode: CPU0: new patch_level=0x010000c8 Oct 28 19:47:08 linux kernel: [ 8.959198] microcode: CPU1: patch_level=0x00000000 Oct 28 19:47:08 linux kernel: [ 8.959764] microcode: CPU1: new patch_level=0x010000c8 Oct 28 19:47:08 linux kernel: [ 8.959776] microcode: CPU2: patch_level=0x00000000 Oct 28 19:47:08 linux kernel: [ 8.960090] microcode: CPU2: new patch_level=0x010000c8 Oct 28 19:47:08 linux kernel: [ 8.960098] microcode: CPU3: patch_level=0x00000000 Oct 28 19:47:08 linux kernel: [ 8.960341] microcode: CPU3: new patch_level=0x010000c8 Oct 28 19:47:08 linux kernel: [ 8.960380] microcode: Microcode Update Driver: v2.00 , Peter Oruba ....[ the boot freezes here when it does freeze (not this time obviously ]... Oct 28 19:47:08 linux kernel: [ 9.076327] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3 Oct 28 19:47:08 linux kernel: [ 9.076384] ACPI: Power Button [PWRB] Oct 28 19:47:08 linux kernel: [ 9.076481] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 Oct 28 19:47:08 linux kernel: [ 9.076544] ACPI: Power Button [PWRF] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mmarek@suse.com |kernel-maintainers@forge.pr | |ovo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c4 --- Comment #4 from Cristian Rodríguez 2013-03-21 12:54:52 CLT --- (In reply to comment #0)

Hi:

I just shoot myself in the foot ! ;)

steps:

- add the microcode module to the initrd /etc/sysconfig/kernel variable INITRD_MODULES

- run mkinitrd (have recovery cd handy)

- reboot

result:

Boot hang, module keeps looping forever and ever.

Expected result:

- either make it work or disallow that module in the initrd.

Now, this is probably moot, what we need is mkinitrd supporting kernel 3.9 's early microcode load.. config MICROCODE_INTEL_EARLY bool "Early load microcode" depends on MICROCODE_INTEL && BLK_DEV_INITRD default y help This option provides functionality to read additional microcode data at the beginning of initrd image. The data tells kernel to load microcode to CPU's as early as possible. No functional change if no microcode data is glued to the initrd, therefore it's safe to say Y. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c5 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpetkov@suse.com --- Comment #5 from Borislav Petkov 2013-07-16 08:22:26 UTC --- Can you guys try the steps at the end of Documentation/x86/early-microcode.txt in the kernel sources? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c7 --- Comment #7 from Borislav Petkov 2013-08-12 06:50:50 UTC --- Ok, this bugzilla got kinda confusing with all the "me too"s. So, let's start afresh: How exactly do I reproduce this? What machine, what kernel + .config attached, please someone explain in as detailed manner as possible what's going on here? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|mknitrd: microcode module |microcode module in initrd |in initrd causes boot hang |causes boot hang -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c Cristian Rodríguez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|crrodriguez@opensuse.org | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c10 --- Comment #10 from Cristian Rodríguez 2013-09-03 11:08:39 CLT --- (In reply to comment #9)

(In reply to comment #8)

...

- Now you *really* need to add the microcode files to the initrd, preferable implemented in the "early microcode" form : https://www.kernel.org/doc/Documentation/x86/early-microcode.txt , why ?

Only Intel can come up with such a process...

Anyway, I have not read the kernel code: Are really two cpio archives required

at least when using dracut to get an initrd with early microcode working, there seems to be two. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c12 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |crrodriguez@opensuse.org --- Comment #12 from Olaf Hering 2013-09-25 15:10:09 CEST --- (In reply to comment #10)

(In reply to comment #9)

...

(In reply to comment #8)

...

- Now you *really* need to add the microcode files to the initrd, preferable implemented in the "early microcode" form : https://www.kernel.org/doc/Documentation/x86/early-microcode.txt , why ?

Only Intel can come up with such a process...

Anyway, I have not read the kernel code: Are really two cpio archives required

at least when using dracut to get an initrd with early microcode working, there seems to be two.

Did you try the suggestion from comment #9? What package contains the microcode anyway? It needs updating to include the mkinitrd.sh scripts. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c14 --- Comment #14 from Dirk Weber 2013-11-23 16:00:33 UTC --- (In reply to comment #13)

Related to bnc#847158 I tried the procedure from comment #9 with 13.1. It does not work - means the microcode is not updated early, please see details in bnc#847158.

For clarification: with 13.1 the early microcode update works (I tested with AMD CPUs) when the initrd is created according to https://www.kernel.org/doc/Documentation/x86/early-microcode.txt but it does not work with an initrd created like described in comment #9. It seems combination of 2 cpio archives is indeed necessary. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761728 https://bugzilla.novell.com/show_bug.cgi?id=761728#c16 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@suse.com --- Comment #16 from Thomas Renninger 2013-11-24 13:13:30 UTC ---

I will add code to compensate for this strange requirement. Please don't. Afaik there isn't any microcode yet, which needs early loading. But there have been the first sever regressions reported:

https://bugzilla.novell.com/show_bug.cgi?id=847158#c18

But early microcode update with a handcrafted initrd (like in comment #11) causes a reboot (everything tested with plain 13.1). So there are still more problems in this area, and just adding the ucodes to the initrd could cause boot problems for users on certain systems. ---------------------- The stuff should be integrated automatically for factory via dracut already. At least for Intel, AMD needs double checking. As this is a new feature introducing sever regressions without any/much benefit, I would not implement this as a maintenance update. Better concentrate that ucode-intel (for Intel) package and kernel-firmware (for AMD) is installed correctly and we should be done. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.