Re: [RFC] Arm64 boot fail with numa enable in BIOS

2016-09-20 Thread Will Deacon
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

Re: [RFC] Arm64 boot fail with numa enable in BIOS

2016-09-19 Thread Yisheng Xie
On 2016/9/20 10:01, Ming Lei wrote: > On Mon, Sep 19, 2016 at 9:05 PM, Yisheng Xie wrote: >> hi all, >> When I enable NUMA in BIOS for arm64, it failed to boot on >> v4.8-rc4-162-g071e31e. >> For the crash log, it seems caused by error number of cpumask. >> Any ideas about it? > > When I playe

Re: [RFC] Arm64 boot fail with numa enable in BIOS

2016-09-19 Thread Yisheng Xie
On 2016/9/19 22:07, Mark Rutland wrote: > [adding LAKML, arm64 maintainers] > > On Mon, Sep 19, 2016 at 09:05:26PM +0800, Yisheng Xie wrote: >> hi all, > > 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 dum

Re: [RFC] Arm64 boot fail with numa enable in BIOS

2016-09-19 Thread Hanjun Guo
On 2016/9/19 22:07, Mark Rutland wrote: > [adding LAKML, arm64 maintainers] > > On Mon, Sep 19, 2016 at 09:05:26PM +0800, Yisheng Xie wrote: >> hi all, > Hi, > > In future, please make sure to Cc LAKML along with relevant parties when > sending arm64 patches/queries. > > For everyone newly Cc'd, th

Re: [RFC] Arm64 boot fail with numa enable in BIOS

2016-09-19 Thread Ming Lei
On Mon, Sep 19, 2016 at 9:05 PM, Yisheng Xie wrote: > hi all, > When I enable NUMA in BIOS for arm64, it failed to boot on > v4.8-rc4-162-g071e31e. > For the crash log, it seems caused by error number of cpumask. > Any ideas about it? When I played v4.7 on ARM64 with NUMA, I saw the same issue[1

Re: [RFC] Arm64 boot fail with numa enable in BIOS

2016-09-19 Thread Leizhen (ThunderTown)
On 2016/9/19 22:45, Will Deacon wrote: > On Mon, Sep 19, 2016 at 03:07:19PM +0100, Mark Rutland wrote: >> [adding LAKML, arm64 maintainers] > > I've also looped in Euler ThunderTown, since (a) he's at Huawei and is > assumedly testing this stuff and (b) he has a fairly big NUMA patch > series do

Re: [RFC] Arm64 boot fail with numa enable in BIOS

2016-09-19 Thread James Morse
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

Re: [RFC] Arm64 boot fail with numa enable in BIOS

2016-09-19 Thread Will Deacon
On Mon, Sep 19, 2016 at 03:07:19PM +0100, Mark Rutland wrote: > [adding LAKML, arm64 maintainers] I've also looped in Euler ThunderTown, since (a) he's at Huawei and is assumedly testing this stuff and (b) he has a fairly big NUMA patch series doing the rounds (some of which I've queued). > On Mo

Re: [RFC] Arm64 boot fail with numa enable in BIOS

2016-09-19 Thread Mark Rutland
[adding LAKML, arm64 maintainers] On Mon, Sep 19, 2016 at 09:05:26PM +0800, Yisheng Xie wrote: > hi all, Hi, In future, please make sure to Cc LAKML along with relevant parties when sending arm64 patches/queries. For everyone newly Cc'd, the original message (with attachments) can be found at: