From: Rik van Riel <riel@surriel.com>
To: "Henrik Böving" <henrik@lean-fro.org>,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org
Cc: linux-kernel@vger.kernel.org,
Sebastian Ullrich <sebastian@lean-fro.org>,
Joscha Mennicken <joscha@lean-fro.org>
Subject: Re: PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB
Date: Mon, 22 Jun 2026 15:00:09 -0400 [thread overview]
Message-ID: <9363eca429424d967052bc401d4d835f1e6d2716.camel@surriel.com> (raw)
In-Reply-To: <CAAuFnRTyva1_3tsF3vrMBL+TLS1YL4EgUPT2c3O9k7A9hWUMnA@mail.gmail.com>
On Fri, 2026-06-19 at 15:17 +0200, Henrik Böving wrote:
> [1.] One line summary of the problem
> Probabilistic segfault on AMD hardware with INVLPGB
>
> [2.] Full description of the problem/report:
>
> Since upgrading from kernel 6.14 to 7.1, we've been observing
> probabilistic segfaults on our build machines. We were able to
> reproduce
> these segfaults on two copies of the same hardware, equipped with an
> AMD EPYC 9455 48-Core Processor. Subsequently, we managed to bisect
> the
> segfault down to the introduction of INVLPGB-based page invalidation
> by
> enabling/disabling BROADCAST_TLB_FLUSH on kernel 6.15. The segfaults
> also do not reproduce on hardware that does not have the INVLPGB
> instruction.
>
We have also seen increased segfault rates when we
first deployed Turin CPUs. This turned out to be
AMD erratum AMD-SB-3029.
Upgrading the firmware on the host solved those
segfaults for us.
Doing a bulk data analysis across the Meta fleet
shows that Turin segfault rates are in the same
range as those of other CPU microarchitectures,
of several vendors.
https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3029.html
Now, it is possible that INVLPGB has increased
the likelihood of hitting some race condition, and
it also possible that the kernel has a TLB
flushing bug somewhere, but it may make sense
to start with a firmware upgrade.
--
All Rights Reversed.
next prev parent reply other threads:[~2026-06-22 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 13:17 Henrik Böving
2026-06-22 19:00 ` Rik van Riel [this message]
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
2026-07-07 16:44 ` Rik van Riel
2026-07-08 15:27 ` Rik van Riel
2026-07-08 15:51 ` Borislav Petkov
2026-09-14 2:20 ` Tal Zussman
2026-09-14 4:58 ` Borislav Petkov
2026-10-02 21:24 ` 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=9363eca429424d967052bc401d4d835f1e6d2716.camel@surriel.com \
--to=riel@surriel.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=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
all inboxes | Powered by JetHome®