From: Thomas Gleixner <tglx@linutronix.de>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Gu Zheng <guz.fnst@cn.fujitsu.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Dou Liyang <douly.fnst@cn.fujitsu.com>
Subject: Re: Bogus "APIC: NR_CPUS/possible_cpus limit of 4 reached" messages
Date: Fri, 7 Oct 2016 15:55:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610071549330.19804@nanos> (raw)
In-Reply-To: <20161007132634.GA20654@x4>
On Fri, 7 Oct 2016, Markus Trippelsdorf wrote:
> On 2016.10.06 at 13:52 +0200, Markus Trippelsdorf wrote:
> > On 2016.10.06 at 12:48 +0100, One Thousand Gnomes wrote:
> > > On Thu, 6 Oct 2016 13:27:37 +0200
> > > Markus Trippelsdorf <markus@trippelsdorf.de> wrote:
> > >
> > > > On current trunk I get during boot:
> > > >
> > > > [ 0.000000] APIC: NR_CPUS/possible_cpus limit of 4 reached. Processor 4/0x84 ignored.
> > > > [ 0.000000] APIC: NR_CPUS/possible_cpus limit of 4 reached. Processor 5/0x85 ignored.
> > > >
> > > > I don't think these messages make much sense on a 4-core machine.
> > > >
> > >
> > > Four cores with or without hyperthreading ?
> >
> > Without. This is a rather old AMD machine (AMD Phenom II X4 955).
That's due to the recent cpuid -> nodeid changes. The patch below should
fix it.
Thanks,
tglx
diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
index f266b8a92a9e..88c657b057e2 100644
--- a/arch/x86/kernel/apic/apic.c
+++ b/arch/x86/kernel/apic/apic.c
@@ -2128,9 +2128,11 @@ int __generic_processor_info(int apicid, int version, bool enabled)
if (num_processors >= nr_cpu_ids) {
int thiscpu = max + disabled_cpus;
- pr_warning(
- "APIC: NR_CPUS/possible_cpus limit of %i reached."
- " Processor %d/0x%x ignored.\n", max, thiscpu, apicid);
+ if (enabled) {
+ pr_warning("APIC: NR_CPUS/possible_cpus limit of %i "
+ "reached. Processor %d/0x%x ignored.\n",
+ max, thiscpu, apicid);
+ }
disabled_cpus++;
return -EINVAL;
next prev parent reply other threads:[~2016-10-07 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 11:27 Bogus "APIC: NR_CPUS/possible_cpus limit of 4 reached" messages Markus Trippelsdorf
2016-10-06 11:48 ` One Thousand Gnomes
2016-10-06 11:52 ` Markus Trippelsdorf
2016-10-07 13:26 ` Markus Trippelsdorf
2016-10-07 13:55 ` Thomas Gleixner [this message]
2016-10-07 14:09 ` Markus Trippelsdorf
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=alpine.DEB.2.20.1610071549330.19804@nanos \
--to=tglx@linutronix.de \
--cc=douly.fnst@cn.fujitsu.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=guz.fnst@cn.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
/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).