From: Richard Weinberger <richard@nod.at>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Christian Ludloff <ludloff@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Sohil Mehta <sohil.mehta@intel.com>,
"Ahmed S. Darwish" <darwi@linutronix.de>, bp <bp@alien8.de>,
x86 <x86@kernel.org>, Thomas Gleixner <tglx@kernel.org>,
mingo <mingo@redhat.com>, hpa <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
andrew cooper3 <andrew.cooper3@citrix.com>,
Tony Luck <tony.luck@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] x86/cpu/intel: Simplify F00F bug notice using pr_notice_once()
Date: Tue, 26 May 2026 22:56:11 +0200 (CEST) [thread overview]
Message-ID: <942991536.24435.1779828971179.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <alpine.DEB.2.21.2605231826450.1450@angie.orcam.me.uk>
----- Ursprüngliche Mail -----
> Von: "Maciej W. Rozycki" <macro@orcam.me.uk>
> An: "Christian Ludloff" <ludloff@gmail.com>
> CC: "richard" <richard@nod.at>, "Dave Hansen" <dave.hansen@intel.com>, "Sohil Mehta" <sohil.mehta@intel.com>, "Ahmed S.
> Darwish" <darwi@linutronix.de>, "bp" <bp@alien8.de>, "x86" <x86@kernel.org>, "Thomas Gleixner" <tglx@kernel.org>,
> "mingo" <mingo@redhat.com>, "hpa" <hpa@zytor.com>, "Josh Poimboeuf" <jpoimboe@kernel.org>, "andrew cooper3"
> <andrew.cooper3@citrix.com>, "Tony Luck" <tony.luck@intel.com>, "linux-kernel" <linux-kernel@vger.kernel.org>
> Gesendet: Montag, 25. Mai 2026 12:41:00
> Betreff: Re: [PATCH v2 2/3] x86/cpu/intel: Simplify F00F bug notice using pr_notice_once()
> On Fri, 22 May 2026, Maciej W. Rozycki wrote:
>
>> (now that I've looked at it again, I can see it's 6.13.0 as it's been a
>> while, so maybe it's gone now in 7.x, hmm... will have to check.)
>
> Yep, still there:
>
> ------------[ cut here ]------------
> Bad FPU state detected at restore_fpregs_from_fpstate+0x48/0x50, reinitializing
> FPU registers.
> WARNING: at fixup_exception+0x2a1/0x2c0, CPU#1: ld-linux.so.2/9621
> CPU: 1 UID: 500 PID: 9621 Comm: ld-linux.so.2 Tainted: G W
> 7.0.0-dirty #1 PREEMPT
> Tainted: [W]=WARN
> Hardware name: [...]
Do you see this also in qemu?
I can give your test a try on my dual Pentium system.
Thanks,
//richard
next prev parent reply other threads:[~2026-05-26 21:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 0:24 [PATCH v2 0/3] x86: Fix a F00F bug warning and cleanup surrounding code Sohil Mehta
2026-05-15 0:24 ` [PATCH v2 1/3] x86/cpu/intel: Don't clear X86_BUG_F00F before setting it Sohil Mehta
2026-05-15 19:16 ` Ahmed S. Darwish
2026-05-15 0:24 ` [PATCH v2 2/3] x86/cpu/intel: Simplify F00F bug notice using pr_notice_once() Sohil Mehta
2026-05-15 19:14 ` Ahmed S. Darwish
2026-05-15 22:37 ` Sohil Mehta
2026-05-15 23:09 ` Ahmed S. Darwish
2026-05-15 23:23 ` Dave Hansen
2026-05-18 20:29 ` Sohil Mehta
2026-05-18 21:17 ` Dave Hansen
2026-05-18 21:23 ` H. Peter Anvin
2026-05-21 22:38 ` Maciej W. Rozycki
2026-05-22 6:11 ` Christian Ludloff
2026-05-22 20:27 ` Maciej W. Rozycki
2026-05-25 10:41 ` Maciej W. Rozycki
2026-05-26 20:56 ` Richard Weinberger [this message]
2026-05-27 0:25 ` Maciej W. Rozycki
2026-05-26 14:14 ` Dave Hansen
2026-05-26 15:01 ` Maciej W. Rozycki
2026-05-26 15:20 ` David Laight
2026-05-26 17:43 ` Christian Ludloff
2026-05-26 19:15 ` Maciej W. Rozycki
2026-05-26 20:49 ` H. Peter Anvin
2026-05-27 0:29 ` Maciej W. Rozycki
2026-05-27 6:13 ` H. Peter Anvin
2026-05-27 9:09 ` David Laight
2026-05-27 9:23 ` Maciej W. Rozycki
2026-05-27 15:36 ` H. Peter Anvin
2026-05-27 16:14 ` Maciej W. Rozycki
2026-06-01 14:43 ` H. Peter Anvin
2026-06-01 21:45 ` David Laight
2026-05-15 0:25 ` [PATCH v2 3/3] x86/cpufeature: Remove clear_cpu_bug() Sohil Mehta
2026-05-15 19:16 ` Ahmed S. Darwish
2026-05-15 6:18 ` [PATCH v2 0/3] x86: Fix a F00F bug warning and cleanup surrounding code Richard Weinberger
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=942991536.24435.1779828971179.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=darwi@linutronix.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludloff@gmail.com \
--cc=macro@orcam.me.uk \
--cc=mingo@redhat.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@kernel.org \
--cc=tony.luck@intel.com \
--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