From: James Morse <james.morse@arm.com>
To: Mark Rutland <mark.rutland@arm.com>,
Yisheng Xie <xieyisheng1@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Hanjun Guo <guohanjun@huawei.com>,
Xishi Qiu <qiuxishi@huawei.com>,
linux-arm-kernel@lists.infradead.org, will.deacon@arm.com,
catalin.marinas@arm.com
Subject: Re: [RFC] Arm64 boot fail with numa enable in BIOS
Date: Mon, 19 Sep 2016 18:41:29 +0100 [thread overview]
Message-ID: <57E02349.10703@arm.com> (raw)
In-Reply-To: <20160919140709.GA17464@leverpostej>
On 19/09/16 15:07, Mark Rutland wrote:
> On Mon, Sep 19, 2016 at 09:05:26PM +0800, Yisheng Xie wrote:
>> For the crash log, it seems caused by error number of cpumask.
>> Any ideas about it?
> Much earlier in your log, there was a (non-fatal) warning, as below. Do
> you see this without NUMA/SRAT enabled in your FW?
>> [ 0.297337] Detected PIPT I-cache on CPU1
>> [ 0.297347] GICv3: CPU1: found redistributor 10001 region 1:0x000000004d140000
>> [ 0.297356] CPU1: Booted secondary processor [410fd082]
>> [ 0.297375] ------------[ cut here ]------------
>> [ 0.320390] WARNING: CPU: 1 PID: 0 at ./include/linux/cpumask.h:121 gic_raise_softirq+0x128/0x17c
>> [ 0.329356] Modules linked in:
>> [ 0.332434]
>> [ 0.333932] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.0-rc4-00163-g803ea3a #21
>> [ 0.341581] Hardware name: Hisilicon Hi1616 Evaluation Board (DT)
>> [ 0.347735] task: ffff8013e9dd0000 task.stack: ffff8013e9dcc000
>> [ 0.353714] PC is at gic_raise_softirq+0x128/0x17c
>> [ 0.358550] LR is at gic_raise_softirq+0xa0/0x17c
I've seen this first trace when built with DEBUG_PER_CPU_MAPS. My version of
this trace[0] was just noise due to gic_compute_target_list() and
gic_raise_softirq() sharing an iterator.
This patch silenced it for me:
https://lkml.org/lkml/2016/9/19/623
Yours may be a different problem with the same symptom.
Thanks,
James
[0] gicv3 trace when built with DEBUG_PER_CPU_MAPS
[ 3.077738] GICv3: CPU1: found redistributor 1 region 0:0x000000002f120000
[ 3.077943] CPU1: Booted secondary processor [410fd0f0]
[ 3.078542] ------------[ cut here ]------------
[ 3.078746] WARNING: CPU: 1 PID: 0 at ../include/linux/cpumask.h:121
gic_raise_softirq+0x12c/0x170
[ 3.078812] Modules linked in:
[ 3.078869]
[ 3.078930] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.0-rc5+ #5188
[ 3.078994] Hardware name: Foundation-v8A (DT)
[ 3.079059] task: ffff80087a1a0080 task.stack: ffff80087a19c000
[ 3.079145] PC is at gic_raise_softirq+0x12c/0x170
[ 3.079226] LR is at gic_raise_softirq+0xa4/0x170
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-09-19 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 13:05 Yisheng Xie
2016-09-19 14:07 ` Mark Rutland
2016-09-19 14:45 ` Will Deacon
2016-09-20 1:19 ` Leizhen (ThunderTown)
2016-09-19 17:41 ` James Morse [this message]
2016-09-20 2:51 ` Hanjun Guo
2016-09-20 3:29 ` Yisheng Xie
2016-09-20 8:33 ` Will Deacon
2016-09-20 2:01 ` Ming Lei
2016-09-20 4:05 ` Yisheng Xie
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=57E02349.10703@arm.com \
--to=james.morse@arm.com \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=qiuxishi@huawei.com \
--cc=will.deacon@arm.com \
--cc=xieyisheng1@huawei.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