From: "Zhang, Rui" <rui.zhang@intel.com>
To: "andres@anarazel.de" <andres@anarazel.de>
Cc: "linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>, "bp@alien8.de" <bp@alien8.de>,
"peterz@infradead.org" <peterz@infradead.org>,
"jsperbeck@google.com" <jsperbeck@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"sashal@kernel.org" <sashal@kernel.org>,
"tip-bot2@linutronix.de" <tip-bot2@linutronix.de>
Subject: Re: [tip: x86/urgent] x86/acpi: Ignore invalid x2APIC entries
Date: Thu, 7 Dec 2023 02:41:34 +0000 [thread overview]
Message-ID: <c3b064004a1748c68829f804b3da56a610fbfc8e.camel@intel.com> (raw)
In-Reply-To: <20231206065850.hs7k554v6wym7gw5@awork3.anarazel.de>
Hi, Andres,
On Tue, 2023-12-05 at 22:58 -0800, Andres Freund wrote:
> Hi,
>
> On 2023-12-01 08:31:48 +0000, Zhang, Rui wrote:
> > As a quick fix, I'm not going to fix the "potential issue"
> > describes
> > above because we have not seen a real problem caused by this yet.
> >
> > Can you please try the below patch to confirm if the problem is
> > gone on
> > your system?
> > This patch falls back to the previous way as sent at
> > https://lore.kernel.org/lkml/87pm4bp54z.ffs@tglx/T/
>
>
> I've just spent a couple hours bisecting why upgrading to 6.7-rc4
> left me with
> just a single CPU core on my dual socket workstation.
>
>
> before:
> [ 0.000000] Linux version 6.6.0-andres-00003-g31255e072b2e ...
> ...
> [ 0.022960] ACPI: Using ACPI (MADT) for SMP configuration
> information
> ...
> [ 0.022968] smpboot: Allowing 40 CPUs, 0 hotplug CPUs
> ...
> [ 0.345921] smpboot: CPU0: Intel(R) Xeon(R) Gold 5215 CPU @
> 2.50GHz (family: 0x6, model: 0x55, stepping: 0x7)
> ...
> [ 0.347229] .... node #0, CPUs: #1 #2 #3 #4 #5 #6
> #7 #8 #9
> [ 0.349082] .... node #1, CPUs: #10 #11 #12 #13 #14 #15 #16 #17
> #18 #19
> [ 0.003190] smpboot: CPU 10 Converting physical 0 to logical die 1
>
> [ 0.361053] .... node #0, CPUs: #20 #21 #22 #23 #24 #25 #26 #27
> #28 #29
> [ 0.363990] .... node #1, CPUs: #30 #31 #32 #33 #34 #35 #36 #37
> #38 #39
> ...
> [ 0.370886] smp: Brought up 2 nodes, 40 CPUs
> [ 0.370891] smpboot: Max logical packages: 2
> [ 0.370896] smpboot: Total of 40 processors activated (200000.00
> BogoMIPS)
> [ 0.403905] node 0 deferred pages initialised in 32ms
> [ 0.408865] node 1 deferred pages initialised in 37ms
>
>
> after:
> [ 0.000000] Linux version 6.6.0-andres-00004-gec9aedb2aa1a ...
> ...
> [ 0.022935] ACPI: Using ACPI (MADT) for SMP configuration
> information
> ...
> [ 0.022942] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
> ...
> [ 0.356424] smpboot: CPU0: Intel(R) Xeon(R) Gold 5215 CPU @
> 2.50GHz (family: 0x6, model: 0x55, stepping: 0x7)
> ...
> [ 0.357098] smp: Bringing up secondary CPUs ...
> [ 0.357107] smp: Brought up 2 nodes, 1 CPU
> [ 0.357108] smpboot: Max logical packages: 1
> [ 0.357110] smpboot: Total of 1 processors activated (5000.00
> BogoMIPS)
> [ 0.726283] node 0 deferred pages initialised in 368ms
> [ 0.774704] node 1 deferred pages initialised in 418ms
>
>
> There does seem to be something off with the ACPI data, when booting
> without
> the patch,
which patch are you referring to? the original patch in this thread?
Does the second patch fixes the problem? I mean the patch at
https://lore.kernel.org/all/904ce2b870b8a7f34114f93adc7c8170420869d1.camel@intel.com/
thanks,
rui
> I do see messages like:
> [ 0.715228] APIC: NR_CPUS/possible_cpus limit of 40 reached.
> Processor 40/0x7f00 ignored.
> [ 0.715231] ACPI: Unable to map lapic to logical cpu number
>
> But other than that, the system has worked for a couple years.
>
>
> It's obviously not good to regress from 2x10/20 cores/threads to a
> single
> core. I guess it's at least somewhat funny to imagine a 2 socket
> system with
> a single core...
>
>
> It seems particularly worrying that this patch has apparently been
> selected
> for -stable:
> https://lore.kernel.org/all/20231122153212.852040-2-sashal@kernel.org/
>
> Even if it didn't have these unintended consequences, it seems like a
> commit
> like this hardly is -stable material?
>
>
> I've attached .config, dmesg of a boot with gec9aedb2aa1a and one
> with
> gec9aedb2aa1a^.
>
> Greetings,
>
> Andres Freund
next prev parent reply other threads:[~2023-12-07 2:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 16:28 [RFC PATCH] " Zhang Rui
2023-07-28 12:51 ` Thomas Gleixner
2023-07-28 12:55 ` Thomas Gleixner
2023-07-28 16:47 ` Zhang, Rui
2023-07-29 7:07 ` Thomas Gleixner
2023-07-31 13:04 ` Zhang, Rui
2023-11-09 13:41 ` [tip: x86/urgent] " tip-bot2 for Zhang Rui
2023-11-22 22:17 ` [PATCH] platform/x86: intel_telemetry: Fix kernel doc descriptions John Sperbeck
2023-11-22 22:18 ` [tip: x86/urgent] x86/acpi: Ignore invalid x2APIC entries John Sperbeck
2023-11-22 22:19 ` John Sperbeck
2023-11-23 12:50 ` Zhang, Rui
2023-12-01 3:25 ` Ashok Raj
2023-12-01 18:08 ` Zhang, Rui
2023-12-01 20:23 ` Ashok Raj
2023-12-02 2:53 ` Zhang, Rui
2023-12-01 8:31 ` Zhang, Rui
2023-12-01 23:32 ` John Sperbeck
2023-12-06 6:58 ` Andres Freund
2023-12-07 2:41 ` Zhang, Rui [this message]
2023-12-07 5:10 ` Andres Freund
2023-12-12 17:34 ` Thomas Gleixner
2023-12-13 7:39 ` Zhang, Rui
2023-12-13 14:51 ` Thomas Gleixner
2023-12-14 15:00 ` Zhang, Rui
2023-12-14 21:11 ` Thomas Gleixner
2023-12-15 14:19 ` [PATCH] x86/acpi: Handle bogus MADT APIC tables gracefully Thomas Gleixner
2023-12-15 14:20 ` [tip: x86/urgent] x86/acpi: Ignore invalid x2APIC entries Andres Freund
2023-12-10 11:47 ` Linux regression tracking (Thorsten Leemhuis)
2023-12-18 13:57 ` [tip: x86/urgent] x86/acpi: Handle bogus MADT APIC tables gracefully tip-bot2 for Thomas Gleixner
2024-10-10 21:31 ` [RFC PATCH] x86/acpi: Ignore invalid x2APIC entries Jim Mattson
2024-10-11 1:37 ` Zhang, Rui
2024-10-11 3:05 ` Jim Mattson
2024-10-14 13:05 ` Zhang, Rui
2024-10-14 18:00 ` Jim Mattson
2024-10-15 3:23 ` Zhang, Rui
2024-10-15 13:26 ` Jim Mattson
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=c3b064004a1748c68829f804b3da56a610fbfc8e.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=andres@anarazel.de \
--cc=bp@alien8.de \
--cc=jsperbeck@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tip-bot2@linutronix.de \
--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
all inboxes | Powered by JetHome®