The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Conrad Kostecki <ck@conrad-kostecki.de>
To: "Linux (Kernel) Mailingliste (linux-kernel@vger.kernel.org)" 
	<linux-kernel@vger.kernel.org>
Subject: AW: Early microcode not being loaded
Date: Mon, 1 Sep 2014 18:21:48 +0000	[thread overview]
Message-ID: <06765c8a9ea84f8a81d595e05dcfe10e@DB4PR04MB265.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <4c348de3b92a49c58bf17777873410dd@DB4PR04MB265.eurprd04.prod.outlook.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 4843 bytes --]

> Hi!
> I'am trying to use the feature of loading early an intel microcode.
> According to the documentation (early-microcode.txt) that should be possible.
>
> I am currently using my own initrd, so I've created a second one, as the docs specified and merged it with my own.
>
> Galactica linux # file /tmp/ucode.cpio
> /tmp/ucode.cpio: ASCII cpio archive (SVR4 with no CRC)
>
> Galactica linux # file /tmp/my_own_initrd.cpio
> /tmp/my_own_initrd.cpio: ASCII cpio archive (SVR4 with no CRC)
>
> Galactica linux #  cpio -itv < /tmp/ucode.cpio
> drwxr-xr-x   3 root     root            0 Jul 18 17:01 .
> drwxr-xr-x   3 root     root            0 Jul 18 17:01 kernel
> drwxr-xr-x   3 root     root            0 Jul 18 17:01 kernel/x86
> drwxr-xr-x   2 root     root            0 Jul 18 17:01 kernel/x86/microcode
> -rw-r--r--   1 root     root      1857432 Jul 18 17:01 kernel/x86/microcode/GenuineIntel.bin
>
> Galactica tmp # cpio -itv < /tmp/my_own_initrd.cpio
> drwxr-xr-x  11 root     root            0 Jul 18 22:33 .
> drwxr-xr-x   3 root     root            0 Jul 18 22:33 mnt
> drwxr-xr-x   2 root     root            0 Jul 18 22:33 mnt/root
> drwxr-xr-x   2 root     root            0 Jul 18 22:33 lib64
> drwxr-xr-x   2 root     root            0 Jul 18 22:33 etc
> drwxr-xr-x   2 root     root            0 Jul 18 22:33 sys
> drwxr-xr-x   2 root     root            0 Jul 18 22:33 bin
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/ash -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/cat -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/loadkmap -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/cut -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/setfont -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/kbd_mode -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/echo -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/umount -> /bin/busybox
> -rwxr-xr-x   1 root     root      2638208 Jul 18 22:33 bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/mount -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/mdev -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/sleep -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 bin/printf -> /bin/busybox
> drwxr-xr-x   3 root     root            0 Jul 18 22:33 usr
> drwxr-xr-x   2 root     root            0 Jul 18 22:33 usr/bin
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 usr/bin/setfont -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 usr/bin/kbd_mode -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 usr/bin/printf -> /bin/busybox
> drwxr-xr-x   3 root     root            0 Jul 18 22:33 dev
> crw-r--r--   1 root     root       5,   1 Jul 18 22:33 dev/console
> crw-r--r--   1 root     root       4,  64 Jul 18 22:33 dev/ttyS0
> crw-r--r--   1 root     root       1,   3 Jul 18 22:33 dev/null
> crw-r--r--   1 root     root       1,   5 Jul 18 22:33 dev/zero
> drwxr-xr-x   2 root     root            0 Jul 18 22:33 proc
> -rwxr-xr-x   1 root     root         5707 Jul 18 22:33 init
> lrwxrwxrwx   1 root     root            5 Jul 18 22:33 lib -> lib64
> drwxr-xr-x   2 root     root            0 Jul 18 22:33 sbin
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 sbin/loadkmap -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 sbin/switch_root -> /bin/busybox
> lrwxrwxrwx   1 root     root           12 Jul 18 22:33 sbin/mdev -> /bin/busybox
> 5174 blocks
>
> Then I merged them, as the docs say:
> cat /tmp/ucode.cpio /tmp/my_own_initrd.cpio > /boot/initramfs-3.15.5.img
>
> Booting works fine with this combined initrd, but there is no new microcode applied.
>
> [    1.058641] microcode: CPU0 sig=0x20661, pf=0x2, revision=0x104
> [    1.063259] microcode: CPU1 sig=0x20661, pf=0x2, revision=0x104
> [    1.068011] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
>
> It's only applied much later, when my microcode_ctl runs as a service.
>
> [   15.764517] microcode: CPU0 sig=0x20661, pf=0x2, revision=0x104
> [   15.764979] microcode: CPU0 updated to revision 0x105, date = 2011-07-18
> [   15.765970] microcode: CPU1 sig=0x20661, pf=0x2, revision=0x104
> [   15.766430] microcode: CPU1 updated to revision 0x105, date = 2011-07-18
>
> Where is the problem? Why is the microcode not being loaded early?
>
> Cheers
> Conrad

Does anybody has some idea, why this is not working for me?
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2014-09-01 18:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 20:40 Early microcode not being loaded Conrad Kostecki
2014-07-18 21:24 ` Borislav Petkov
2014-07-18 21:49   ` AW: " Conrad Kostecki
2014-09-01 18:21     ` Conrad Kostecki [this message]
2014-09-01 20:17       ` Henrique de Moraes Holschuh
2014-09-01 20:36         ` AW: " Conrad Kostecki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=06765c8a9ea84f8a81d595e05dcfe10e@DB4PR04MB265.eurprd04.prod.outlook.com \
    --to=ck@conrad-kostecki.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox