All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Gu Zheng <guz.fnst@cn.fujitsu.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Bogus "APIC: NR_CPUS/possible_cpus limit of 4 reached" messages
Date: Thu, 6 Oct 2016 13:27:37 +0200	[thread overview]
Message-ID: <20161006112737.GA308@x4> (raw)

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.

-- 
Markus

             reply	other threads:[~2016-10-06 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 11:27 Markus Trippelsdorf [this message]
2016-10-06 11:48 ` Bogus "APIC: NR_CPUS/possible_cpus limit of 4 reached" messages One Thousand Gnomes
2016-10-06 11:52   ` Markus Trippelsdorf
2016-10-07 13:26     ` Markus Trippelsdorf
2016-10-07 13:55       ` Thomas Gleixner
2016-10-07 14:09         ` Markus Trippelsdorf
2016-10-08 10:24         ` [tip:x86/urgent] x86/apic: Prevent pointless warning messages tip-bot 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=20161006112737.GA308@x4 \
    --to=markus@trippelsdorf.de \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.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.