[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161007140926.GA314@x4>
Date: Fri, 7 Oct 2016 16:09:26 +0200
From: Markus Trippelsdorf <markus@...ppelsdorf.de>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Gu Zheng <guz.fnst@...fujitsu.com>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org,
Dou Liyang <douly.fnst@...fujitsu.com>
Subject: Re: Bogus "APIC: NR_CPUS/possible_cpus limit of 4 reached" messages
On 2016.10.07 at 15:55 +0200, Thomas Gleixner wrote:
> 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@...ppelsdorf.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.
Indeed it does. Thanks for the quick fix.
--
Markus
Powered by blists - more mailing lists