From: Sohil Mehta <sohil.mehta@intel.com>
To: "Dave Hansen" <dave.hansen@intel.com>,
"Laurențiu Păncescu" <lpancescu@gmail.com>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Eric Biggers <ebiggers@google.com>,
<linux-kernel@vger.kernel.org>, <1117002@bugs.debian.org>
Subject: Re: WARNING: CPU: 1 PID: 0 at arch/x86/kernel/cpu/cpuid-deps.c:123 do_clear_cpu_cap+0xdc/0x130 on Intel(R) Atom(TM) CPU N450 system
Date: Fri, 17 Oct 2025 15:44:11 -0700 [thread overview]
Message-ID: <9f0ff555-860c-4e3a-9865-b921b0f7d187@intel.com> (raw)
In-Reply-To: <45a02791-dcb9-4d70-ad77-4fdcbf556c15@intel.com>
On 10/17/2025 3:01 PM, Dave Hansen wrote:
> I'm not quite sure why newer kernels are complaining. The
> "alternatives_patched" check has been around since ~6.10. If someone has
> some spare time on their hands, they could bisect it. But I'm not sure
> it will change anything.
>
I would bet on commit 15b7ddcf66fb ("x86/cpu/intel: Fix fast string
initialization for extended Families"). It started honoring the
preference set in MSR_IA32_MISC_ENABLE which seems to have unmasked this
issue.
The commit has the following snippet:
"X86_FEATURE_REP_GOOD is cleared in early_init_intel() if
MISC_ENABLE.FAST_STRING is 0. But it gets set later on unconditionally
for all Family 6 processors in init_intel(). This not only overrides the
BIOS preference but also contradicts the earlier check.
Fix this by combining the related checks and always relying on the BIOS
provided preference for fast string operations."
next prev parent reply other threads:[~2025-10-18 2:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 14:05 Salvatore Bonaccorso
2025-10-17 14:26 ` Dave Hansen
2025-10-17 21:02 ` Laurențiu Păncescu
[not found] ` <45a02791-dcb9-4d70-ad77-4fdcbf556c15@intel.com>
2025-10-17 22:44 ` Sohil Mehta [this message]
2025-11-27 12:37 ` Dominik 'Rathann' Mierzejewski
2025-12-01 17:54 ` Dave Hansen
2025-12-01 20:29 ` Dominik 'Rathann' Mierzejewski
2025-10-17 15:36 ` Andi Kleen
2025-10-17 15:52 ` Sohil Mehta
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=9f0ff555-860c-4e3a-9865-b921b0f7d187@intel.com \
--to=sohil.mehta@intel.com \
--cc=1117002@bugs.debian.org \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=carnil@debian.org \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lpancescu@gmail.com \
--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 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®