All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem with late AMD microcode reload/feedback
Date: Sun, 16 Dec 2018 09:08:00 +0100	[thread overview]
Message-ID: <bac495ca-ccfd-3551-97ca-1444a391fa40@gmail.com> (raw)
In-Reply-To: <20181216000510.GC6693@zn.tnic>

On 16.12.2018 01:05, Borislav Petkov wrote:
> On Sun, Dec 16, 2018 at 12:46:05AM +0100, Rafał Miłecki wrote:
>> [19.736770] microcode: [find_equiv_id] sig:8458000
> 
> That's your CPU's family/model/stepping: 0x0810f10
> 
>> [19.736772] microcode: [find_equiv_id] equiv_table->installed_cpu:8392466
>> [19.736775] microcode: [find_equiv_id] equiv_table->installed_cpu:8392578
> 
> and those are present on the system. Best to look at them in hex, btw:
> 
> 0x0800f12
> 0x0800f82
> 
> Which means, there's no microcode for your CPU so nothing gets updated.

Thanks! I had no idea microcode_amd_fam17h.bin is a container with few
microcodes. I thought there is a single microcode for a whole family
(e.g. 17h).

Using hex also makes more sense indeed!
[   44.127941] microcode: verify_and_add_patch: Added patch_id: 0x08001227, proc_id: 0x8012
[   44.127948] microcode: verify_and_add_patch: Added patch_id: 0x0800820b, proc_id: 0x8082
[   44.127952] microcode: [find_equiv_id] sig:0x810f10
[   44.127955] microcode: [find_equiv_id] equiv_table->installed_cpu:0x800f12
[   44.127958] microcode: [find_equiv_id] equiv_table->installed_cpu:0x800f82

So for now I'm stuck with the default/BIOS-uploaded microcode:
[    2.604680] microcode: CPU0: patch_level=0x0810100b
[    2.605617] microcode: CPU1: patch_level=0x0810100b
[    2.606583] microcode: CPU2: patch_level=0x0810100b
[    2.607528] microcode: CPU3: patch_level=0x0810100b
[    2.608408] microcode: CPU4: patch_level=0x0810100b
[    2.609285] microcode: CPU5: patch_level=0x0810100b
[    2.610270] microcode: CPU6: patch_level=0x0810100b
[    2.611135] microcode: CPU7: patch_level=0x0810100b

I've one more hacking idea. My notebook has Ryzen 5 PRO 2500U CPU but I
also have access to another one with Ryzen 5 2500U running:
[    2.780949] microcode: CPU0: patch_level=0x08101007

For my hack tests I'd like to replace my 0x0810100b with a 0x08101007.
Is that possible to extract/dump current microcode from the CPU and
package it as microcode_amd_fam17h.bin?

Are there any ready tools for that?

  reply	other threads:[~2018-12-16  8:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 23:46 Problem with late AMD microcode reload/feedback Rafał Miłecki
2018-12-16  0:05 ` Borislav Petkov
2018-12-16  8:08   ` Rafał Miłecki [this message]
2018-12-16 10:06     ` Borislav Petkov
2018-12-16 10:26       ` Rafał Miłecki
2018-12-16 10:44         ` Borislav Petkov
2018-12-16 11:02           ` Rafał Miłecki
2018-12-16 11:12             ` Borislav Petkov
2018-12-16  0:08 ` 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=bac495ca-ccfd-3551-97ca-1444a391fa40@gmail.com \
    --to=zajec5@gmail.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.