From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Arm64 boot fail with numa enable in BIOS
Date: Tue, 20 Sep 2016 09:33:52 +0100 [thread overview]
Message-ID: <20160920083352.GA25614@arm.com> (raw)
In-Reply-To: <cd53a1ae-e4ff-933c-4d1c-1ddaaa999a43@huawei.com>
Hi Yisheng,
On Tue, Sep 20, 2016 at 11:29:24AM +0800, Yisheng Xie wrote:
> On 2016/9/19 22:07, Mark Rutland wrote:
> > On Mon, Sep 19, 2016 at 09:05:26PM +0800, Yisheng Xie wrote:
> > Can you modify the warning in cpumask.h to dump the bad CPU number? That
> > would make it fairly clear if that's the case.
> >
> hi Mark,
> I dump the bad CPU number, it is 64,
> And the cpumask get from task is 00000000,00000000.
>
> [ 3.873044] select_task_rq: allowed 0, allow_cpumask 00000000,00000000
> [ 3.879727] cpumask_check: cpu 64, nr_cpumask_bits:64, nr_cpu_ids= 64
> [ 3.895989] ------------[ cut here ]------------
> [ 3.900652] WARNING: CPU: 16 PID: 103 at ./include/linux/cpumask.h:122 try_to_wake_up+0x410/0x4ac
Can you look at this patch from David, please:
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-September/458110.html
and offer a Tested-by if it fixes your problem?
Thanks,
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
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, catalin.marinas@arm.com
Subject: Re: [RFC] Arm64 boot fail with numa enable in BIOS
Date: Tue, 20 Sep 2016 09:33:52 +0100 [thread overview]
Message-ID: <20160920083352.GA25614@arm.com> (raw)
In-Reply-To: <cd53a1ae-e4ff-933c-4d1c-1ddaaa999a43@huawei.com>
Hi Yisheng,
On Tue, Sep 20, 2016 at 11:29:24AM +0800, Yisheng Xie wrote:
> On 2016/9/19 22:07, Mark Rutland wrote:
> > On Mon, Sep 19, 2016 at 09:05:26PM +0800, Yisheng Xie wrote:
> > Can you modify the warning in cpumask.h to dump the bad CPU number? That
> > would make it fairly clear if that's the case.
> >
> hi Mark,
> I dump the bad CPU number, it is 64,
> And the cpumask get from task is 00000000,00000000.
>
> [ 3.873044] select_task_rq: allowed 0, allow_cpumask 00000000,00000000
> [ 3.879727] cpumask_check: cpu 64, nr_cpumask_bits:64, nr_cpu_ids= 64
> [ 3.895989] ------------[ cut here ]------------
> [ 3.900652] WARNING: CPU: 16 PID: 103 at ./include/linux/cpumask.h:122 try_to_wake_up+0x410/0x4ac
Can you look at this patch from David, please:
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-September/458110.html
and offer a Tested-by if it fixes your problem?
Thanks,
Will
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
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, catalin.marinas@arm.com
Subject: Re: [RFC] Arm64 boot fail with numa enable in BIOS
Date: Tue, 20 Sep 2016 09:33:52 +0100 [thread overview]
Message-ID: <20160920083352.GA25614@arm.com> (raw)
In-Reply-To: <cd53a1ae-e4ff-933c-4d1c-1ddaaa999a43@huawei.com>
Hi Yisheng,
On Tue, Sep 20, 2016 at 11:29:24AM +0800, Yisheng Xie wrote:
> On 2016/9/19 22:07, Mark Rutland wrote:
> > On Mon, Sep 19, 2016 at 09:05:26PM +0800, Yisheng Xie wrote:
> > Can you modify the warning in cpumask.h to dump the bad CPU number? That
> > would make it fairly clear if that's the case.
> >
> hi Mark,
> I dump the bad CPU number, it is 64,
> And the cpumask get from task is 00000000,00000000.
>
> [ 3.873044] select_task_rq: allowed 0, allow_cpumask 00000000,00000000
> [ 3.879727] cpumask_check: cpu 64, nr_cpumask_bits:64, nr_cpu_ids= 64
> [ 3.895989] ------------[ cut here ]------------
> [ 3.900652] WARNING: CPU: 16 PID: 103 at ./include/linux/cpumask.h:122 try_to_wake_up+0x410/0x4ac
Can you look at this patch from David, please:
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-September/458110.html
and offer a Tested-by if it fixes your problem?
Thanks,
Will
next prev parent reply other threads:[~2016-09-20 8:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 13:05 [RFC] Arm64 boot fail with numa enable in BIOS Yisheng Xie
2016-09-19 13:05 ` Yisheng Xie
2016-09-19 14:07 ` Mark Rutland
2016-09-19 14:07 ` Mark Rutland
2016-09-19 14:07 ` Mark Rutland
2016-09-19 14:45 ` Will Deacon
2016-09-19 14:45 ` Will Deacon
2016-09-19 14:45 ` Will Deacon
2016-09-20 1:19 ` Leizhen (ThunderTown)
2016-09-20 1:19 ` Leizhen (ThunderTown)
2016-09-20 1:19 ` Leizhen (ThunderTown)
2016-09-19 17:41 ` James Morse
2016-09-19 17:41 ` James Morse
2016-09-19 17:41 ` James Morse
2016-09-20 2:51 ` Hanjun Guo
2016-09-20 2:51 ` Hanjun Guo
2016-09-20 2:51 ` Hanjun Guo
2016-09-20 3:29 ` Yisheng Xie
2016-09-20 3:29 ` Yisheng Xie
2016-09-20 3:29 ` Yisheng Xie
2016-09-20 8:33 ` Will Deacon [this message]
2016-09-20 8:33 ` Will Deacon
2016-09-20 8:33 ` Will Deacon
2016-09-20 2:01 ` Ming Lei
2016-09-20 2:01 ` Ming Lei
2016-09-20 4:05 ` Yisheng Xie
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=20160920083352.GA25614@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.