From: Thomas Gleixner <tglx@linutronix.de>
To: Lyude Paul <lyude@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Early boot regression from f0551af0213 ("x86/topology: Ignore non-present APIC IDs in a present package")
Date: Thu, 18 Apr 2024 21:13:34 +0200 [thread overview]
Message-ID: <87plumxz4x.ffs@tglx> (raw)
In-Reply-To: <fd040809d95b3e12b2fdc78a2409e187716bc66f.camel@redhat.com>
On Thu, Apr 18 2024 at 13:20, Lyude Paul wrote:
> Just gave it a try, unfortunately I'm still seeing the same result on
> that branch.
>
> One more piece of information I apparently missed when reporting this
> yesterday btw: I noticed one more kernel message that comes before the
> panic that's probably relevant:
>
> ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Can you please apply the debug patch below which should make it boot
again.
Please also provide the output of the files underneath of
/sys/kernel/debug/x86/topo/
Thanks,
tglx
---
arch/x86/kernel/cpu/topology.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
--- a/arch/x86/kernel/cpu/topology.c
+++ b/arch/x86/kernel/cpu/topology.c
@@ -176,6 +176,8 @@ static __init void topo_register_apic(u3
{
int cpu, dom;
+ pr_info("APIC ID %x present %d\n", apic_id, present);
+
if (present) {
set_bit(apic_id, phys_cpu_present_map);
@@ -201,10 +203,7 @@ static __init void topo_register_apic(u3
*/
if (hypervisor_is_type(X86_HYPER_NATIVE) &&
topo_unit_count(pkgid, TOPO_PKG_DOMAIN, phys_cpu_present_map)) {
- pr_info_once("Ignoring hot-pluggable APIC ID %x in present package.\n",
- apic_id);
- topo_info.nr_rejected_cpus++;
- return;
+ pr_info("Hot-pluggable APIC ID %x in present package.\n", apic_id);
}
topo_info.nr_disabled_cpus++;
next prev parent reply other threads:[~2024-04-18 19:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 21:21 Early boot regression from f0551af0213 ("x86/topology: Ignore non-present APIC IDs in a present package") Lyude Paul
2024-04-18 8:27 ` Borislav Petkov
2024-04-18 17:20 ` Lyude Paul
2024-04-18 19:13 ` Thomas Gleixner [this message]
2024-04-19 5:37 ` Thomas Gleixner
2024-04-19 17:38 ` Lyude Paul
2024-04-19 22:15 ` Thomas Gleixner
2024-04-23 17:09 ` Thomas Gleixner
2024-04-24 20:56 ` Lyude Paul
2024-04-25 2:11 ` Thomas Gleixner
2024-04-25 15:56 ` Lyude Paul
2024-04-25 21:42 ` Thomas Gleixner
2024-05-02 10:33 ` Mario Limonciello
2024-05-08 8:38 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-08 10:30 ` Thomas Gleixner
2024-05-08 21:02 ` Lyude Paul
2024-05-08 23:21 ` Lyude Paul
2024-05-13 14:08 ` Thomas Gleixner
2024-05-13 23:18 ` Lyude Paul
2024-05-13 23:32 ` Lyude Paul
2024-05-14 8:25 ` Thomas Gleixner
2024-05-15 23:15 ` Lyude Paul
2024-05-16 13:38 ` Thomas Gleixner
2024-05-22 19:35 ` Lyude Paul
2024-05-22 22:12 ` Thomas Gleixner
2024-05-23 5:20 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-23 10:47 ` Thomas Gleixner
2024-05-28 22:43 ` Thomas Gleixner
2024-06-03 16:22 ` Lyude Paul
2024-06-05 23:15 ` Lyude Paul
2024-06-06 9:50 ` Thomas Gleixner
2024-05-09 19:22 ` Lyude Paul
2024-05-08 21:47 ` Thomas Gleixner
2024-05-08 22:09 ` Mario Limonciello
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=87plumxz4x.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.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