All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: 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: Thu, 30 May 2024 10:30:09 +0200	[thread overview]
Message-ID: <87zfs78zxq.ffs@tglx> (raw)
In-Reply-To: <ce3abe01-4c37-416e-a5ed-25703318318a@googlemail.com>

Peter!

On Mon, May 27 2024 at 23:15, Peter Schneider wrote:

Thanks for providing all the information!

> I want to add one thing: there is a log entry in the dmesg output of a "bad" kernel, which 
> I initially overlooked, because it is way up, and I noticed this just now. I guess this 
> might be relevant:
>
> [    1.683564] [Firmware Bug]: CPU0: Topology domain 0 shift 1 != 5

Yes. That's absolutely related. I can see what goes wrong, but I have
absolutely no idea how that happens.

Can you please apply the debug patch below ad provide the full dmesg
after boot?

Thanks,

        tglx
---
--- a/arch/x86/kernel/cpu/topology_common.c
+++ b/arch/x86/kernel/cpu/topology_common.c
@@ -65,6 +65,7 @@ static void parse_legacy(struct topo_sca
 		cores <<= smt_shift;
 	}
 
+	pr_info("Legacy: %u %u %u\n", c->cpuid_level, smt_shift, core_shift);
 	topology_set_dom(tscan, TOPO_SMT_DOMAIN, smt_shift, 1U << smt_shift);
 	topology_set_dom(tscan, TOPO_CORE_DOMAIN, core_shift, cores);
 }
--- a/arch/x86/kernel/cpu/topology_ext.c
+++ b/arch/x86/kernel/cpu/topology_ext.c
@@ -72,6 +72,9 @@ static inline bool topo_subleaf(struct t
 
 	cpuid_subleaf(leaf, subleaf, &sl);
 
+	pr_info("L:%0x %0x %0x S:%u N:%u T:%u\n", leaf, subleaf, sl.level, sl.x2apic_shift,
+		sl.num_processors, sl.type);
+
 	if (!sl.num_processors || sl.type == INVALID_TYPE)
 		return false;
 
@@ -97,6 +100,7 @@ static inline bool topo_subleaf(struct t
 			     leaf, subleaf, tscan->c->topo.initial_apicid, sl.x2apic_id);
 	}
 
+	pr_info("D: %u\n", dom);
 	topology_set_dom(tscan, dom, sl.x2apic_shift, sl.num_processors);
 	return true;
 }

  parent reply	other threads:[~2024-05-30  8:30 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 [this message]
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
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=87zfs78zxq.ffs@tglx \
    --to=tglx@linutronix.de \
    --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 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.