From: Borislav Petkov <bp@alien8.de>
To: Conrad Kostecki <ck@conrad-kostecki.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Early microcode not being loaded
Date: Fri, 18 Jul 2014 23:24:27 +0200 [thread overview]
Message-ID: <20140718212427.GB11098@pd.tnic> (raw)
In-Reply-To: <d01572d84b834e9d98aef338f7da446a@DB4PR04MB265.eurprd04.prod.outlook.com>
On Fri, Jul 18, 2014 at 08:40:42PM +0000, Conrad Kostecki wrote:
> Where is the problem? Why is the microcode not being loaded early?
CONFIG_MICROCODE_INTEL_EARLY=y set in .config?
You can also try with a recent distro kernel and initrd which has
microcode in it to rule out you're doing something wrong when generating
the initrd.
HTH.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-07-18 21:24 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 [this message]
2014-07-18 21:49 ` AW: " Conrad Kostecki
2014-09-01 18:21 ` Conrad Kostecki
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=20140718212427.GB11098@pd.tnic \
--to=bp@alien8.de \
--cc=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