From: Gabriel C <nix.or.die@gmail.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: AMD EPYC microcode update bug?
Date: Wed, 10 Jan 2018 00:37:48 +0100 [thread overview]
Message-ID: <59bfc45e-0741-2a45-fa5c-9b148b22e4ca@gmail.com> (raw)
In-Reply-To: <CAEJqkggKwp09nZB8E-VrDQH_giUBiJnn23NGFCXZW2X+NOaaBg@mail.gmail.com>
On 10.01.2018 00:06, Gabriel C wrote:
> 2018-01-09 23:47 GMT+01:00 Tom Lendacky <thomas.lendacky@amd.com>:
>> On 1/9/2018 4:28 PM, Gabriel C wrote:
>>> Hello ,
>>>
>>> I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors.
>>>
>>> I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin.
>>>
>>> First run was made by using the early microcode option with dracut[1]
>>> so loading from a initrd. the driver reported 63 updated CPUs while CPU0
>>> got still old microcode.
>>
>> I'm guessing that memory encryption is enabled, correct? I've submitted a
>> patch series to perform early initrd decryption for just this problem. I'm
>> incorporating some minor feedback and getting ready to submit the next
>> version.
>
> Yes is correct I use mem_encrypt=on and SMT on in BIOS.
>
> Can you give me an link to the patch series ?
>
>>
>> In the meantime, if you specify mem_encrypt=off on the kernel command line
>> it should show CPU0 updated properly (with mem_encrypt=on and SMT enabled,
>> I believe it really does get updated when the sibling hread is updated -
>> do a rdmsr of 0x0000008b to verify).
>>
>
> I give that an test in a bit , the box is running now some test for a
> different EPYC issue :)
>
> ( https://community.amd.com/thread/224000 )
>
With mem_encrypt=off all is working fine from a initrd with SMT ON
Reagrds,
Gabriel C
next prev parent reply other threads:[~2018-01-09 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 22:28 Gabriel C
2018-01-09 22:47 ` Tom Lendacky
2018-01-09 23:06 ` Gabriel C
2018-01-09 23:37 ` Gabriel C [this message]
2018-01-09 23:44 ` Tom Lendacky
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=59bfc45e-0741-2a45-fa5c-9b148b22e4ca@gmail.com \
--to=nix.or.die@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
/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
all inboxes | Powered by JetHome®