Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp7815884imu; Thu, 15 Nov 2018 01:53:30 -0800 (PST) X-Google-Smtp-Source: AJdET5cbHOrx2T3m6yeDaD6C2FhrtE7YwYrcYz5M8HmdMlW9/hRvMCRyZXcFyk9Ngn+OkWsYsCYC X-Received: by 2002:a63:981:: with SMTP id 123mr5184075pgj.444.1542275610427; Thu, 15 Nov 2018 01:53:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542275610; cv=none; d=google.com; s=arc-20160816; b=kEIUHRw3VtFxUp9Y7aNWvMPnFlZhpR9XY092oQD3wGXwJry5gDBYN+bhgIqVNicVV/ 2wOnAzYYj3EaFDzSvpp8/ZVuAT7VMHDyX1KEbgjZkma1cerwLtZ048EJ+iWMc/AWzPQl LdQO67xZDtDF/EkArei385Dgzq4cK5nyV42fKuoi211bEvgH5F3WSm4RP8JOVJi0609c zkUuDLDUdoIfiEvNME7A23yXDmU/etfVQqCI32p5ZMAaXN324PIFhKBpYGJxxsfiJp+V jKGIx6lagsg1xr/IKEP/+BY8A7RGukP7Vcgl8Q6e4tg51oiV034qVRo9Q5NMeadXhUWj at2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=vUlsaZmswjHPk+HInRVKwQ8DJeGHm8ch0tFz9Kw/zMs=; b=IMnzw4RakbFJQH7Xj2/cP/nws1qduMLinmvw7Obozy2a8FquiawobsZSd3aU6cNHwb pc8OEGoyEL8PtPUvCLtqVAixiI9fS+4LTOlSWd2+T3sGJG1sZPIqCtlqGt8kJCM/RemB xIpJpKqg3IKzEWGDlOR9mc8GG29BVmckUktn8IhkBH3bNv9skhoR7BdzI47wiHuqnW21 dzteqHKfI5IDwuhjbk7rzMndcs1eVTvu6F5KQb3AoroflQ/+nev0ZCo4PWVg4NcBy49I 7BMnSN5PCCimtoeMmPre9lV+7rfZ8+WM1u40M22ARrMbJ3JEUxsYrZ5+SdJLowC9QXnd 4lyw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i62si3105122pgd.556.2018.11.15.01.53.14; Thu, 15 Nov 2018 01:53:30 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729083AbeKOT7l (ORCPT + 99 others); Thu, 15 Nov 2018 14:59:41 -0500 Received: from mx1.redhat.com ([209.132.183.28]:50150 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728634AbeKOT7l (ORCPT ); Thu, 15 Nov 2018 14:59:41 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 47C34A0C02; Thu, 15 Nov 2018 09:52:35 +0000 (UTC) Received: from localhost (ovpn-8-20.pek2.redhat.com [10.72.8.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9C0BB1057058; Thu, 15 Nov 2018 09:52:28 +0000 (UTC) Date: Thu, 15 Nov 2018 17:52:25 +0800 From: Baoquan He To: David Hildenbrand Cc: Michal Hocko , linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, aarcange@redhat.com Subject: Re: Memory hotplug softlock issue Message-ID: <20181115095225.GO2653@MiWiFi-R3L-srv> References: <20181114070909.GB2653@MiWiFi-R3L-srv> <5a6c6d6b-ebcd-8bfa-d6e0-4312bfe86586@redhat.com> <20181114090134.GG23419@dhcp22.suse.cz> <20181114145250.GE2653@MiWiFi-R3L-srv> <20181114150029.GY23419@dhcp22.suse.cz> <20181115051034.GK2653@MiWiFi-R3L-srv> <20181115073052.GA23831@dhcp22.suse.cz> <20181115075349.GL2653@MiWiFi-R3L-srv> <20181115083055.GD23831@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Thu, 15 Nov 2018 09:52:35 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/15/18 at 10:42am, David Hildenbrand wrote: > I am wondering why it is always the last memory block of that device > (and even that node). Coincidence? I remember one or two times it's the last 6G or 4G which stall there, the size of memory block is 2G. But most of time it's the last memory block. And from the debug printing added by Michal's patch, it's the stress program itself which owns the migrating page and loop forvever there.