From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Nick Bowler <nbowler@elliptictech.com>,
linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: the maxcpus= boot parameter broke somewhere along the line
Date: Wed, 04 Apr 2012 12:32:42 +0530 [thread overview]
Message-ID: <4F7BF212.3040005@linux.vnet.ibm.com> (raw)
In-Reply-To: <x49sjgmgpwc.fsf@segfault.boston.devel.redhat.com>
On 04/02/2012 08:08 PM, Jeff Moyer wrote:
> "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com> writes:
>
>> On 04/02/2012 07:35 PM, Jeff Moyer wrote:
>>
>>> "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com> writes:
>>>
>>>> Looking at the mention of udev above, and considering the commit you bisected
>>>> to, I think it would be good to see whether someone is writing 1 to
>>>> /sys/device/system/cpu/cpu*/online and hence the cpus are getting hot-added
>>>> towards the end of boot. Maybe that sounds stupid, but worth a try :)
>>>>
>>>> So can you try the debug patch below? It applies on latest linux-3.3-rc6+
>>>
>>> Sorry it took me so long to get back to you. You're patch did, in fact,
>>> trigger:
>>>
>>> udev: starting version 147
>>> CPU 3 online initated from userspace
>>> SMP alternatives: switching to SMP code
>>> WARNING! power/level is deprecated; use power/control instead
>>> Booting Node 0 Processor 3 APIC 0x3
>>> NMI watchdog: enabled, takes one hw-pmu counter.
>>> CPU 1 online initated from userspace
>>> Booting Node 0 Processor 1 APIC 0x2
>>> NMI watchdog: enabled, takes one hw-pmu counter.
>>> CPU 2 online initated from userspace
>>> Booting Node 0 Processor 2 APIC 0x1
>>> NMI watchdog: enabled, takes one hw-pmu counter.
>>> CPU 1 online initated from userspace
>>> CPU 3 online initated from userspace
>>> CPU 2 online initated from userspace
>>>
>>
>>
>> Aha! Just like I thought!
>> So there is no kernel bug with respect to the maxcpus= boot parameter :-)
>
> But this IS a change in behaviour (using older kernels, the maxcpus=
> boot parameter works just fine).
Hmmm.. strange...
> So, what exactly has changed is my
> question, and what is the right way to fix it?
>
I am not sure about the root cause of this behaviour change.
I also observed (in the logs above) that the "CPU X online initiated from
userspace" message appears *twice* for each CPU! Could that give somebody
a hint on what might be going wrong, hopefully?
Maybe it would be good to compare the above logs with the logs produced
from the older kernels that work as expected.
Regards,
Srivatsa S. Bhat
prev parent reply other threads:[~2012-04-04 7:03 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
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 [this message]
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=4F7BF212.3040005@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=jmoyer@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@elliptictech.com \
/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).