public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: AMD microcode loading broken on 32 bit
Date: Tue, 21 Jan 2014 17:14:38 +0100	[thread overview]
Message-ID: <20140121161438.GD9004@pd.tnic> (raw)
In-Reply-To: <52DE94A9.9060505@oracle.com>

On Tue, Jan 21, 2014 at 10:39:21AM -0500, Boris Ostrovsky wrote:
> I was thinking this could have been introduced by last night's merge
> of your tree.

Ok, I need more info:

* kernel .config

* are you building an initrd with the microcode? If so, how exactly?
Which microcode blob?

* what machine, family?

* anything else I'd need to reproduce here?

Btw, why the h*ll are you still using a 32-bit kernel? :)

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

       reply	other threads:[~2014-01-21 16:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52DE94A9.9060505@oracle.com>
2014-01-21 16:14 ` Borislav Petkov [this message]
2014-01-21 17:55   ` AMD microcode loading broken on 32 bit Boris Ostrovsky
2014-01-21 18:25     ` Borislav Petkov
2014-01-23 18:08       ` Boris Ostrovsky
2014-01-23 18:54         ` Gene Heskett
2014-01-23 19:09           ` Boris Ostrovsky
2014-01-23 19:36             ` Gene Heskett
2014-01-23 19:29         ` Borislav Petkov
2014-01-23 19:41           ` Boris Ostrovsky
2014-01-28 16:24             ` Borislav Petkov
2014-01-28 20:43               ` Boris Ostrovsky
2014-01-28 20:52                 ` Borislav Petkov
2014-01-28 21:05                   ` Boris Ostrovsky
2014-01-28 21:30                     ` Borislav Petkov
2014-01-28 21:37                       ` Boris Ostrovsky
2014-01-28 23:10                         ` Boris Ostrovsky
2014-01-28 23:22                           ` Borislav Petkov
2014-01-30 15:13                             ` Borislav Petkov
2014-01-30 19:41                               ` Boris Ostrovsky
2014-01-30 19:54                                 ` Borislav Petkov
2014-02-03 17:55                                   ` [PATCH -v2] x86, microcode, AMD: Sanity-check initrd image Borislav Petkov
2014-02-03 19:13                                     ` Boris Ostrovsky
2014-02-03 19:30                                       ` Borislav Petkov
2014-02-03 19:37                                         ` Boris Ostrovsky
2014-02-03 19:52                                           ` Borislav Petkov
2014-02-03 20:28                                             ` Boris Ostrovsky
2014-02-03 20:33                                               ` Borislav Petkov
2014-02-03 20:41                                                 ` [PATCH] x86, microcode, AMD: Unify valid container checks Borislav Petkov
2014-02-06 19:39                                                   ` [tip:x86/urgent] " tip-bot for Borislav Petkov

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=20140121161438.GD9004@pd.tnic \
    --to=bp@alien8.de \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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