From: Aaro Koskinen <aaro.koskinen@nokia.com>
To: Yang Shi <yang.shi@windriver.com>, david.daney@cavium.com
Cc: linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: 4.5-rc4 kernel is failed to bootup on CN6880
Date: Mon, 22 Feb 2016 14:43:03 +0200 [thread overview]
Message-ID: <20160222124303.GR22974@ak-desktop.emea.nsn-net.net> (raw)
In-Reply-To: <56C7BD89.2040800@windriver.com>
Hi,
On Fri, Feb 19, 2016 at 05:12:41PM -0800, Yang Shi wrote:
> I tried to boot 4.5-rc4 kernel on my CN6880 board, but it is failed at
> booting up secondary cores. The error is:
With v4.5-rc5, EBB6800 is booting fine:
[ 0.000000] CPU0 revision is: 000d9108 (Cavium Octeon II)
[...]
[ 2286.273935] SMP: Booting CPU01 (CoreId 1)...
[ 2286.278201] CPU1 revision is: 000d9108 (Cavium Octeon II)
[...]
[ 2287.214953] SMP: Booting CPU31 (CoreId 31)...
[ 2287.224668] CPU31 revision is: 000d9108 (Cavium Octeon II)
[ 2287.224865] Brought up 32 CPUs
> CPU31 revision is: 000d9101 (Cavium Octeon II)
> SMP: Booting CPU32 (CoreId 32)...
> Secondary boot timeout
>
> I passed "numcores=32" in kernel commandline since there are 32 cores ion
> CN6880.
You shouldn't have CPU32 in that case, the numbering starts from zero.
Also the coremask is 32-bit.
I can reproduce your issue with CONFIG_NR_CPUS=64. Possibly this code
is incorrect for NR_CPUS bigger than 32:
/* The present CPUs get the lowest CPU numbers. */
cpus = 1;
for (id = 0; id < NR_CPUS; id++) {
if ((id != coreid) && (core_mask & (1 << id))) {
set_cpu_possible(cpus, true);
set_cpu_present(cpus, true);
What CONFIG_NR_CPUS did you use?
A.
next prev parent reply other threads:[~2016-02-22 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 1:12 4.5-rc4 kernel is failed to bootup on CN6880 Yang Shi
2016-02-20 1:15 ` David Daney
2016-02-20 1:19 ` Yang Shi
2016-02-22 12:43 ` Aaro Koskinen [this message]
2016-02-22 19:15 ` Yang Shi
2016-02-22 20:56 ` David Daney
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=20160222124303.GR22974@ak-desktop.emea.nsn-net.net \
--to=aaro.koskinen@nokia.com \
--cc=david.daney@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=yang.shi@windriver.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).