From: Andrew Cooper <andrew.cooper3@citrix.com>
To: henrik@lean-fro.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
dave.hansen@linux.intel.com, joscha@lean-fro.org,
linux-kernel@vger.kernel.org, luto@kernel.org,
peterz@infradead.org, riel@surriel.com, sebastian@lean-fro.org
Subject: Re: PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB
Date: Tue, 23 Jun 2026 14:47:29 +0100 [thread overview]
Message-ID: <2b0ef5cd-ba1f-4ff2-8910-9031e93835b2@citrix.com> (raw)
In-Reply-To: <CAAuFnRR6dmDqjvgatJ1Lu2ZC31LS1QiAcO=djRFOaSiMZdhS0g@mail.gmail.com>
> Thanks for the quick response!
>> Upgrading the firmware on the host solved those segfaults for us.
> Our hardware is currently on microcode version 0x0B002162, while the
> advisory you linked names 0x0B00211E as the patched version for our
> model. So I think we should already be sufficiently up to date for this
> patch, but I don't know (and couldn't find anything on the web) about
> the details of AMD microcode versioning.
AMD microcode version is the bottom byte. The higher bytes are actually
Family/Model/Stepping on all recent CPUs.
So, as for your CPU, the 0xb0021xx part means Turin (non-dense) C1
stepping, and revision 0x62 is the latest available in linux-firmware.
Either way, you're fixed to AMD-SB-3029
~Andrew
next prev parent reply other threads:[~2026-06-23 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 13:17 PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB Henrik Böving
2026-06-22 19:00 ` Rik van Riel
2026-06-23 12:28 ` Henrik Böving
2026-06-23 13:47 ` Andrew Cooper [this message]
2026-06-23 15:59 ` Rik van Riel
2026-07-07 12:18 ` Matt Fleming
2026-07-07 13:45 ` Henrik Böving
2026-07-07 14:11 ` Rik van Riel
2026-07-08 14:51 ` Dave Hansen
2026-07-07 16:44 ` Rik van Riel
2026-07-08 15:27 ` Rik van Riel
2026-07-08 15:51 ` Borislav Petkov
2026-07-08 16:17 ` Borislav Petkov
2026-07-09 7:21 ` Matt Fleming
2026-07-09 19:17 ` 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=2b0ef5cd-ba1f-4ff2-8910-9031e93835b2@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=dave.hansen@linux.intel.com \
--cc=henrik@lean-fro.org \
--cc=joscha@lean-fro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=sebastian@lean-fro.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