From: Dave Hansen <dave.hansen@intel.com>
To: Rik van Riel <riel@surriel.com>, Matt Fleming <matt@readmodwrite.com>
Cc: "Henrik Böving" <henrik@lean-fro.org>,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, linux-kernel@vger.kernel.org,
"Sebastian Ullrich" <sebastian@lean-fro.org>,
"Joscha Mennicken" <joscha@lean-fro.org>,
kernel-team@cloudflare.com, "Borislav Petkov" <bp@alien8.de>,
"Tom Lendacky" <thomas.lendacky@amd.com>
Subject: Re: PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB
Date: Wed, 8 Jul 2026 07:51:32 -0700 [thread overview]
Message-ID: <ab8f5e0a-04d8-45bc-a3fc-91cf37336edd@intel.com> (raw)
In-Reply-To: <1e4ab5c5f64b3bddc0773cf305708500abc66999.camel@surriel.com>
On 7/7/26 07:11, Rik van Riel wrote:
>> ./repro-invlpgb --batch --rounds 20 --jobs 32 -d 5 -w 8 -m 2 -s 512
>> -q
>>
> Now that's interesting. I ran it for 100 rounds on
> a 158 core Turin system, without hitting the issue.
>
> I'll play around with it some more to see whether
> I can make it happen by varying the parameters,
> but now I'm also wondering whether hardware
> differences might be at play.
The first thing I'd check is if you have the _exact_ same model,
stepping and (especially) microcode version.
BTW, it seems like the 'x86 mm' maintainers are cc'd here, but not the
core x86 folks, so you missed Boris. They should probably be keeping an
eye on this too.
next prev parent reply other threads:[~2026-07-08 14:51 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
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 [this message]
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=ab8f5e0a-04d8-45bc-a3fc-91cf37336edd@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=henrik@lean-fro.org \
--cc=joscha@lean-fro.org \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=matt@readmodwrite.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=sebastian@lean-fro.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