From: Thomas Gleixner <tglx@linutronix.de>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>,
Peter Schneider <pschneider1968@googlemail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, stable@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: Kernel 6.9 regression: X86: Bogus messages from topology detection
Date: Sat, 01 Jun 2024 09:20:56 +0200 [thread overview]
Message-ID: <87mso56sdj.ffs@tglx> (raw)
In-Reply-To: <1e26effd-a142-44f5-9a72-90a823666d7c@leemhuis.info>
On Sat, Jun 01 2024 at 09:06, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 31.05.24 10:42, Thomas Gleixner wrote:
>> On Fri, May 31 2024 at 10:33, Thomas Gleixner wrote:
>
>> ---
>> Subject: x86/topology/intel: Unlock CPUID before evaluating anything
>> From: Thomas Gleixner <tglx@linutronix.de>
>> Date: Thu, 30 May 2024 17:29:18 +0200
>>
>> Intel CPUs have a MSR bit to limit CPUID enumeration to leaf two. If this
>> bit is set by the BIOS then CPUID evaluation including topology enumeration
>> does not work correctly as the evaluation code does not try to analyze any
>> leaf greater than two.
>> [...]
>
> TWIMC, I noticed a bug report with a "12 × 12th Gen Intel® Core™
> i7-1255U" where the reporter also noticed a lot of messages like these:
>
> archlinux kernel: [Firmware Bug]: CPU4: Topology domain 1 shift 7 != 6
> archlinux kernel: [Firmware Bug]: CPU4: Topology domain 2 shift 7 != 6
> archlinux kernel: [Firmware Bug]: CPU4: Topology domain 3 shift 7 != 6
>
> Asked the reporter to test this patch. For details see:
> https://bugzilla.kernel.org/show_bug.cgi?id=218879
Won't help. See: https://lore.kernel.org/all/87plt26m2b.ffs@tglx/
Thanks,
tglx
next prev parent reply other threads:[~2024-06-01 7:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 7:29 Kernel 6.9 regression: X86: Bogus messages from topology detection Peter Schneider
2024-05-27 13:14 ` Thomas Gleixner
2024-05-27 20:49 ` Thomas Gleixner
2024-05-27 21:06 ` Peter Schneider
2024-05-27 21:15 ` Peter Schneider
2024-05-27 21:34 ` Christian Heusel
2024-05-30 8:30 ` Thomas Gleixner
2024-05-30 10:06 ` Peter Schneider
2024-05-30 13:35 ` Thomas Gleixner
2024-05-30 15:53 ` Thomas Gleixner
2024-05-30 16:24 ` Thomas Gleixner
2024-05-31 6:52 ` Peter Schneider
2024-05-31 8:33 ` Thomas Gleixner
2024-05-31 8:42 ` Thomas Gleixner
2024-05-31 9:41 ` Peter Schneider
2024-05-31 10:07 ` Thomas Gleixner
2024-05-31 10:22 ` Peter Schneider
2024-06-01 7:06 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-01 7:20 ` Thomas Gleixner [this message]
2024-06-01 7:25 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-31 8:13 ` Christian Heusel
2024-05-31 8:16 ` Christian Heusel
2024-05-31 8:48 ` Thomas Gleixner
2024-05-31 9:11 ` Thomas Gleixner
2024-05-31 13:08 ` Christian Heusel
2024-05-31 13:42 ` Thomas Gleixner
2024-05-31 14:29 ` Christian Heusel
2024-05-31 15:25 ` Thomas Gleixner
2024-05-31 11:06 ` Thomas Gleixner
2024-05-31 19:02 ` [tip: x86/urgent] x86/topology/intel: Unlock CPUID before evaluating anything tip-bot2 for Thomas Gleixner
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=87mso56sdj.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pschneider1968@googlemail.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.