Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757978AbeAIXhx (ORCPT + 1 other); Tue, 9 Jan 2018 18:37:53 -0500 Received: from mail-wm0-f49.google.com ([74.125.82.49]:41377 "EHLO mail-wm0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751926AbeAIXhw (ORCPT ); Tue, 9 Jan 2018 18:37:52 -0500 X-Google-Smtp-Source: ACJfBouhkuhYrFWfrVCtEH4BUqO2kEzi40F+bSRsVWiNl41hOtn1iCVgYe7z3ZL5ibEz6j7SgNWQTg== Subject: Re: AMD EPYC microcode update bug? From: Gabriel C To: Tom Lendacky Cc: LKML , Borislav Petkov References: <997def1f-c8d6-15e3-3505-2a4a78b072ab@amd.com> Message-ID: <59bfc45e-0741-2a45-fa5c-9b148b22e4ca@gmail.com> Date: Wed, 10 Jan 2018 00:37:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On 10.01.2018 00:06, Gabriel C wrote: > 2018-01-09 23:47 GMT+01:00 Tom Lendacky : >> 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