public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Gene Heskett <gheskett@wdtv.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: AMD microcode loading broken on 32 bit
Date: Thu, 23 Jan 2014 14:09:43 -0500	[thread overview]
Message-ID: <52E168F7.7090709@oracle.com> (raw)
In-Reply-To: <201401231354.06952.gheskett@wdtv.com>

On 01/23/2014 01:54 PM, Gene Heskett wrote:
> On Thursday 23 January 2014, Boris Ostrovsky wrote:
>> On 01/21/2014 01:25 PM, Borislav Petkov wrote:
>>> On Tue, Jan 21, 2014 at 12:55:53PM -0500, Boris Ostrovsky wrote:
>>>>           cat $(AMD_UCODE_PATH)/* >
>>>>
>>>> ucode_initrd/kernel/x86/microcode/AuthenticAMD.bin
>>>>
>>>>           (cd ucode_initrd;find . | cpio -o -H newc >
>>>>
>>>> ../$(DISTDIR)/common/ucode_initrd.cpio)
>>>>
>>>>           ...
>>>>           cat $(DISTDIR)/common/ucode_initrd.cpio \
>>>>           
>>>>               $(DISTDIR)/common/_initramfs.cpio.gz > \
>>>>               $(DISTDIR)/common/initramfs.cpio.gz
>>>>
>>>> and as I just discovered, with a little twist: apparently
>>>> AMD_UCODE_PATH points to Intel microcode.
>>> LOL!
>>>
>>> @hpa: in case you were wondering whether Intel ucode works on AMD - it
>>> doesn't! :-)
>>>
>>>> So we clearly screwed up on our end but I'd think that we shouldn't
>>>> crash when this happens.
>>> Yes, we shouldn't. I'll try to reproduce it here.
>> So I tried this on a "good" system and I am pretty sure this is broken.
>> I don't
>> have any microcode in initrd and I am still dying in
>> load_microcode_amd().
> You can find the code on AMD's web site if you look carefully, or at least
> I was able to some years ago when I built this box.  There s/b an installer
> that lives in /etc/init.d, and the code itself normally lives in the
> /lib/firmware/amd-ucode/ directory.
>
> If its working correctly you should see something resembling this in your
> dmsg with:
> gene@coyote$ grep microcode  /var/log/dmesg
> [   22.572212] microcode: CPU0: patch_level=0x01000065
> [   22.573242] microcode: CPU0: new patch_level=0x01000083
> [   22.573256] microcode: CPU1: patch_level=0x01000065
> [   22.573263] microcode: CPU1: new patch_level=0x01000083
> [   22.573273] microcode: CPU2: patch_level=0x01000065
> [   22.573281] microcode: CPU2: new patch_level=0x01000083
> [   22.573293] microcode: CPU3: patch_level=0x01000065
> [   22.573301] microcode: CPU3: new patch_level=0x01000083
> [   22.573377] microcode: Microcode Update Driver: v2.00
> <tigran@aivazian.fsnet.co.uk>, Peter Oruba
>
> That was from a bootup to 3.12.6, 32 bit PAE, on a quad core phenom.

Right. But the (suspected) regression is from this Monday's merge
of early microcode loading code.

-boris


  reply	other threads:[~2014-01-23 19:09 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 ` AMD microcode loading broken on 32 bit Borislav Petkov
2014-01-21 17:55   ` 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 [this message]
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=52E168F7.7090709@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=gheskett@wdtv.com \
    --cc=hpa@zytor.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