From: Dave Hansen <dave.hansen@intel.com>
To: Dominik 'Rathann' Mierzejewski <dominik@greysector.net>
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>,
"Laurențiu Păncescu" <lpancescu@gmail.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Sohil Mehta" <sohil.mehta@intel.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: Mon, 1 Dec 2025 09:54:00 -0800 [thread overview]
Message-ID: <d0be2023-1dd4-4465-8153-d0f3f426a217@intel.com> (raw)
In-Reply-To: <aShGJfVxuHqRZr1l@amaterasu.greysector.net>
On 11/27/25 04:37, Dominik 'Rathann' Mierzejewski wrote:
>> Could you boot the system on a known good kernel and run this, please?
>>
>> rdmsr -a 0x000001a0
>>
>> That'll dump out MSR_IA32_MISC_ENABLE on all the CPUs.
> # rdmsr -a 0x000001a0
> 60840488
> 60840488
> 60840488
> 60840489
I don't think there's any other way to read this than: the BIOS is buggy
and mis-programmed this MSR on one of the CPUs. We can shut the warning
up, of course. But it _is_ a quite valid warning.
I'm just not sure how much code we want to add to the kernel to silence
a warning on 15-year-old CPUs with buggy BIOSes.
Are there any ill effects other than the warning splat?
next prev parent reply other threads:[~2025-12-01 17:54 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
2025-11-27 12:37 ` Dominik 'Rathann' Mierzejewski
2025-12-01 17:54 ` Dave Hansen [this message]
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=d0be2023-1dd4-4465-8153-d0f3f426a217@intel.com \
--to=dave.hansen@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@linux.intel.com \
--cc=dominik@greysector.net \
--cc=ebiggers@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lpancescu@gmail.com \
--cc=mingo@redhat.com \
--cc=sohil.mehta@intel.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®