From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8C169C11D3D for ; Thu, 27 Feb 2020 18:26:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 63A0620726 for ; Thu, 27 Feb 2020 18:26:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1582828016; bh=n6lWamS2Am5VwPl4wt23dPiR41lP5xlpzropXAHvZjk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=ER8bx40AUKgtXRsMx8LIDJb+U9lCRd8/+MgzBGoKRqGtSbuNQJu0yLApIaL6zmgwb m9JhJhJjftyDd/pT4GyL/XTG9e+NEJk265DfILfMi8Xqga4wN4GCjLKp2z7bujVrA9 bukODonhMwdCyoI47mzMF6HSNWGh4j51NAsI4npU= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729317AbgB0S04 (ORCPT ); Thu, 27 Feb 2020 13:26:56 -0500 Received: from mail-wm1-f68.google.com ([209.85.128.68]:51152 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729258AbgB0S0z (ORCPT ); Thu, 27 Feb 2020 13:26:55 -0500 Received: by mail-wm1-f68.google.com with SMTP id a5so502791wmb.0 for ; Thu, 27 Feb 2020 10:26:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=nuYWGvXIJxnKaPJUN7O6fqH652rzQXPhnsvypnDtqKs=; b=T5krsejAiXTorzdRUzUCiVaUW5By7YoR21QHlUlqj27wYatLOBfRsiBJ/J2811FIIl 2R09TqBx2cbkQqdmRj/EBZEcb3MIrDc8V+J3qYyxneZIPUvB291GXV6kT3CxjSKtgs5R hJ0lBM/JEnCRHvLILb9pQRYGcwxddi45oZ7GtDiKFjEU8HE0kekSW3Ei/NZ1J6iUyWkN qPiDj7sbHarnHatziUtk2Sdv6iQWwsWw6mZVMqSa/i3IJy2PjYMz+1kAfyCU+O2yLn2u TDq4GHpfTKZgYEQvd7kgeVeixGpbHiv3JprpYEceIm2ErJEEqVNATYx/H4JAHwcx//Hs i9xA== X-Gm-Message-State: APjAAAWKfHAAE/iGyKn8YRwD/FPzCk7FMRhvGAey1NpGP8wKITkHBXat 2Hl1AhqsTNVxHrMhGVOowN4= X-Google-Smtp-Source: APXvYqx82ijERbvyDfB3ZxoT7lm5HutF/9NedvT6IjWQepUKymCSU7QWzkD1heIcOCKUVN7tFyWCjg== X-Received: by 2002:a1c:67c3:: with SMTP id b186mr108626wmc.36.1582828014406; Thu, 27 Feb 2020 10:26:54 -0800 (PST) Received: from localhost (ip-37-188-246-93.eurotel.cz. [37.188.246.93]) by smtp.gmail.com with ESMTPSA id g7sm1739081wrm.72.2020.02.27.10.26.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 27 Feb 2020 10:26:53 -0800 (PST) Date: Thu, 27 Feb 2020 19:26:50 +0100 From: Michal Hocko To: Vlastimil Babka Cc: Sachin Sant , Pekka Enberg , Linux-Next Mailing List , David Rientjes , Christopher Lameter , linuxppc-dev@lists.ozlabs.org, Joonsoo Kim , Kirill Tkhai , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman Subject: Re: [5.6.0-rc2-next-20200218/powerpc] Boot failure on POWER9 Message-ID: <20200227182650.GG3771@dhcp22.suse.cz> References: <20200218152441.GH4151@dhcp22.suse.cz> <20200224085812.GB22443@dhcp22.suse.cz> <20200226184152.GQ3771@dhcp22.suse.cz> <20200227121214.GE3771@dhcp22.suse.cz> <52EF4673-7292-4C4C-B459-AF583951BA48@linux.vnet.ibm.com> <9a86f865-50b5-7483-9257-dbb08fecd62b@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9a86f865-50b5-7483-9257-dbb08fecd62b@suse.cz> Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org [Cc ppc maintainers] On Thu 27-02-20 17:16:41, Vlastimil Babka wrote: > On 2/27/20 5:00 PM, Sachin Sant wrote: > > > > > >> On 27-Feb-2020, at 5:42 PM, Michal Hocko wrote: > >> > >> A very good hint indeed. I would do this > >> diff --git a/include/linux/topology.h b/include/linux/topology.h > >> index eb2fe6edd73c..d9f1b6737e4d 100644 > >> --- a/include/linux/topology.h > >> +++ b/include/linux/topology.h > >> @@ -137,6 +137,8 @@ static inline void set_numa_mem(int node) > >> { > >> this_cpu_write(_numa_mem_, node); > >> _node_numa_mem_[numa_node_id()] = node; > >> + pr_info("%s %d -> %d\n", __FUNCTION__, numa_node_id(), node); > >> + dump_stack(); > >> } > >> #endif > >> > >> Btw. it would be also helpful to get > >> `faddr2line ___slab_alloc+0x334' from your kernel Sachin. > > > > [linux-next]# ./scripts/faddr2line ./vmlinux ___slab_alloc+0x334 > > ___slab_alloc+0x334/0x760: > > new_slab_objects at mm/slub.c:2478 > > (inlined by) ___slab_alloc at mm/slub.c:2628 > > [linux-next]# > > Hmm that doesn't look relevant, but that address was marked as unreliable, no? > Don't we actually need this one? > > [ 8.768727] NIP [c0000000003d55f4] ___slab_alloc+0x1f4/0x760 > > > I have also attached boot log with a kernel that include about change. > > I see the following o/p during boot: > > > > [ 0.005269] set_numa_mem 1 -> 1 > > So there's no "set_numa_mem 0 -> X", specifically not > "set_numa_mem 0 -> 1" which I would have expected. That seems to confirm my > suspicion that the arch code doesn't set up the memoryless node 0 properly. Please have a look at http://lkml.kernel.org/r/52EF4673-7292-4C4C-B459-AF583951BA48@linux.vnet.ibm.com for the boot log with the debugging patch which tracks set_numa_mem. This seems to lead to a crash in the slab allocator bebcause node_to_mem_node(0) for memory less node resolves to the memory less node http://lkml.kernel.org/r/dd450314-d428-6776-af07-f92c04c7b967@suse.cz. The original report is http://lkml.kernel.org/r/3381CD91-AB3D-4773-BA04-E7A072A63968@linux.vnet.ibm.com > > > [ 0.005270] CPU: 12 PID: 0 Comm: swapper/12 Not tainted 5.6.0-rc3-next-20200227-autotest+ #6 > > [ 0.005271] Call Trace: > > [ 0.005272] [c0000008b37dfe80] [c000000000b5d948] dump_stack+0xbc/0x104 (unreliable) > > [ 0.005274] [c0000008b37dfec0] [c000000000059320] start_secondary+0x600/0x6e0 > > [ 0.005277] [c0000008b37dff90] [c00000000000ac54] start_secondary_prolog+0x10/0x14 > > > > Thanks > > -Sachin > > -- Michal Hocko SUSE Labs