From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752924AbcITIdz (ORCPT ); Tue, 20 Sep 2016 04:33:55 -0400 Received: from foss.arm.com ([217.140.101.70]:51742 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932586AbcITIdv (ORCPT ); Tue, 20 Sep 2016 04:33:51 -0400 Date: Tue, 20 Sep 2016 09:33:52 +0100 From: Will Deacon To: Yisheng Xie Cc: Mark Rutland , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Hanjun Guo , Xishi Qiu , linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com Subject: Re: [RFC] Arm64 boot fail with numa enable in BIOS Message-ID: <20160920083352.GA25614@arm.com> References: <7618d76d-bfa8-d8aa-59aa-06f9d90c1a98@huawei.com> <20160919140709.GA17464@leverpostej> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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