From: Nick Bowler <nbowler@elliptictech.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Jeff Moyer <jmoyer@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: the maxcpus= boot parameter broke somewhere along the line
Date: Tue, 6 Mar 2012 11:48:35 -0500 [thread overview]
Message-ID: <20120306164835.GA26094@elliptictech.com> (raw)
In-Reply-To: <CA+1xoqe_xS95xKM2=X-Mq-_gc+DqzxF2D8YiuCf=0=7=mVKsyw@mail.gmail.com>
On 2012-03-06 17:17 +0200, Sasha Levin wrote:
> On Tue, Mar 6, 2012 at 4:59 PM, Jeff Moyer <jmoyer@redhat.com> wrote:
> > When booting my machine with maxcpus=1, it seems to be ignored with
> > 3.3.0-rc3. I know that 3.1.0-rc3 works fine, but I haven't had time to
> > track it down any further than that. I've attached the dmesg from my
> > machine. Let me know if there is any other information that would help
> > in solving this.
>
> [snip]
>
> > Brought up 1 CPUs
> > Total of 1 processors activated (4256.06 BogoMIPS).
>
> Looks like it indeed brings up only one CPU, what's the problem there?
If you scroll further down it seems that the remaining CPUs are brought
online near the end of the boot?
[...]
udev: starting version 147
SMP alternatives: switching to SMP code
WARNING! power/level is deprecated; use power/control instead
EDAC MC: Ver: 2.1.0
Booting Node 0 Processor 3 APIC 0x3
smpboot cpu 3: start_ip = 9a000
EDAC MC0: Giving out device to 'i3200_edac' 'i3200': DEV 0000:00:00.0
NMI watchdog enabled, takes one hw-pmu counter.
Booting Node 0 Processor 2 APIC 0x1
smpboot cpu 2: start_ip = 9a000
NMI watchdog enabled, takes one hw-pmu counter.
Booting Node 0 Processor 1 APIC 0x2
smpboot cpu 1: start_ip = 9a000
NMI watchdog enabled, takes one hw-pmu counter.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2012-03-06 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 14:59 the maxcpus= boot parameter broke somewhere along the line Jeff Moyer
2012-03-06 15:17 ` Sasha Levin
2012-03-06 16:08 ` Jeff Moyer
2012-03-06 16:48 ` Nick Bowler [this message]
2012-03-06 17:15 ` Sasha Levin
2012-03-06 18:08 ` Jeff Moyer
2012-03-07 15:41 ` Srivatsa S. Bhat
2012-03-07 19:14 ` Jeff Moyer
2012-03-09 11:22 ` Srivatsa S. Bhat
2012-04-02 14:05 ` Jeff Moyer
2012-04-02 14:32 ` Srivatsa S. Bhat
2012-04-02 14:38 ` Jeff Moyer
2012-04-04 7:02 ` Srivatsa S. Bhat
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=20120306164835.GA26094@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=jmoyer@redhat.com \
--cc=levinsasha928@gmail.com \
--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 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).