Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751848AbbH1FUt (ORCPT ); Fri, 28 Aug 2015 01:20:49 -0400 Received: from mail-io0-f182.google.com ([209.85.223.182]:35402 "EHLO mail-io0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750965AbbH1FUr convert rfc822-to-8bit (ORCPT ); Fri, 28 Aug 2015 01:20:47 -0400 MIME-Version: 1.0 In-Reply-To: <26D4DE95-B579-442D-AF7B-469CC4403C51@numascale.com> References: <26D4DE95-B579-442D-AF7B-469CC4403C51@numascale.com> Date: Thu, 27 Aug 2015 22:20:47 -0700 X-Google-Sender-Auth: 150_8_EX5GCOBMuBE9grJN41Pzs Message-ID: Subject: Re: CONFIG_HOLES_IN_ZONE and memory hot plug code on x86_64 From: Yinghai Lu To: Steffen Persvold Cc: x86 , LKML Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 921 Lines: 21 On Fri, Jun 26, 2015 at 4:31 PM, Steffen Persvold wrote: > We’ve encountered an issue in a special case where we have a sparse E820 map [1]. > > Basically the memory hotplug code is causing a “kernel paging request” BUG [2]. the trace does not look like hotplug path. > > By instrumenting the function register_mem_sect_under_node() in drivers/base/node.c we see that it is called two times with the same struct memory_block argument : > > [ 1.901463] register_mem_sect_under_node: start = 80, end = 8f, nid = 0 > [ 1.908129] register_mem_sect_under_node: start = 80, end = 8f, nid = 1 Can you post whole log with SRAT related info? Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/