From: Thomas Gleixner <tglx@linutronix.de>
To: Christian Heusel <christian@heusel.eu>
Cc: Peter Schneider <pschneider1968@googlemail.com>,
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: Fri, 31 May 2024 13:06:50 +0200 [thread overview]
Message-ID: <87wmna6y0l.ffs@tglx> (raw)
In-Reply-To: <20ec1c1a-b804-408f-b279-853579bffc24@heusel.eu>
On Fri, May 31 2024 at 10:16, Christian Heusel wrote:
> On 24/05/31 10:13AM, Christian Heusel wrote:
> [ 0.046127] TSC deadline timer available
> [ 0.046129] CPU topo: Max. logical packages: 1
> [ 0.046129] CPU topo: Max. logical dies: 1
> [ 0.046129] CPU topo: Max. dies per package: 1
> [ 0.046131] CPU topo: Max. threads per core: 2
> [ 0.046132] CPU topo: Num. cores per package: 10
> [ 0.046132] CPU topo: Num. threads per package: 12
> [ 0.046132] CPU topo: Allowing 12 present CPUs plus 0 hotplug CPUs
This looks correct.
> [ 0.117308] smpboot: x86: Booting SMP configuration:
> [ 0.117308] .... node #0, CPUs: #2 #4 #5 #6 #7 #8 #9 #10 #11
> [ 0.009676] [Firmware Bug]: CPU4: Topology domain 1 shift 7 != 6
So this means that the E-Cores have a different topology information for
the CORE shift value than the P-Cores which is definitely wrong.
Let's see what cpuid -r reports.
Thanks,
tglx
prev parent reply other threads:[~2024-05-31 11:07 UTC|newest]
Thread overview: 29+ 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
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 [this message]
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=87wmna6y0l.ffs@tglx \
--to=tglx@linutronix.de \
--cc=christian@heusel.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=pschneider1968@googlemail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).