Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp338659ybi; Fri, 24 May 2019 04:44:53 -0700 (PDT) X-Google-Smtp-Source: APXvYqwQQvVFstdUtb1ZdFnMHWXVXdV52yicG9FmHQDCmjdGrDbWY9KPX37E+KYdT/2G4jojqi2J X-Received: by 2002:a17:902:7797:: with SMTP id o23mr25291606pll.147.1558698293634; Fri, 24 May 2019 04:44:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558698293; cv=none; d=google.com; s=arc-20160816; b=K+oog5zc8vdDLXx/pfkl0gBipOyT3TTRjTVXvP3WixtIg9DHkHPhBbQ/4AIgnUdLrD bCkXTvgi8JES52pq4PQ/uafPAuy2oWK+2TfnfW6oHjH8OlCzUWA+wZbjfk6FbfN0COX6 civYnBbrwx/b3WXNUSC09cjkcN02O/MI9OjfaPBJn0q5O+E7YlfwmiMQow5yqmnJROBm u79TpI0E2scn2EbuI+AFpuyUfcFcRAyhkxROEVPBVhXw2jUX5LrxMNXF1PZktVzm24GO JuAsgWOxYugjrmrwBfxMgeVqs4lF3s7z/M6tcbvQ7zGmObVBSLDtjTzB7JJ3V8fgzEzm 9DBg== 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=aQ5Notts0BAv9aikRNQKLy1psUiEzig1oST72IhaGow=; b=vVGhpsPm0sQ0+aZYt8Uzdgc4AATmsVzovcc7zie0TQUb/dA7pEbhjieMjwrWJ931sq ADhPr4j9d+lyj1aHGIB46QfCoked717TbmsYR3vbt+wcgg0PHxj7VSf2y+YAFpuI9aPo u46lw8SWQuJbaWWKtK09zvPIv0Ys3Q4IaGDUDfMicUfuiOwXbLxT8d02xQbjHrCVXQbH lfCLFBNoajZCqYJZfkIEzUBPUZpVPRdL9COaB9tFADMwhLo4yaUClMI72MBA7osxRgKZ SikiMEhkC5TfJfONeldOIy1EGgikQ94hwtjA+EJ9Y9UqdGUc3StsZlFbwYExApOfVPxD fWTw== 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 co12si4115744plb.384.2019.05.24.04.44.38; Fri, 24 May 2019 04:44:53 -0700 (PDT) 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 S2391214AbfEXLnP (ORCPT + 99 others); Fri, 24 May 2019 07:43:15 -0400 Received: from mail-wm1-f52.google.com ([209.85.128.52]:35719 "EHLO mail-wm1-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390920AbfEXLnO (ORCPT ); Fri, 24 May 2019 07:43:14 -0400 Received: by mail-wm1-f52.google.com with SMTP id w9so2777254wmi.0 for ; Fri, 24 May 2019 04:43:13 -0700 (PDT) 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:user-agent; bh=aQ5Notts0BAv9aikRNQKLy1psUiEzig1oST72IhaGow=; b=SNSGOPprwVKCrwRJJSj2pDWUOnlUGflmmHVZOsX99cADIvadSjy7kDVt9teLeWbpkV 7/56/m4EH4BUg+mUqlrMz9wRyaUX1s/KeGxDXwV8eVzPGfDG21DpX9ObvGRJVZDVkdje pJAObpl8PnTrXaBQ36ucFgEYw0Rn0a+uFmd+qL/LcTchka7rLnlNN2Cxq9lqVQE+deoj pi0kXW7oinJWwaewJrh0NZe/qslcyHs6FscLelhIZI1tyfSrVNMPKoj/7eQ5ykB6znS7 LOHWg0D9Xp39ULkGCw6O+FwZIuF4ubDVtHvruypeqt4P3oMWlNaZwV0NDlkAoGOSIRrj hn3A== X-Gm-Message-State: APjAAAXoLtfLt2sIEFEby76FJ/huDBEBxxekD0EpyhHkYDhZDUglQkJg QL14lo+0orEzsOqoVUy981P7QmzT/r4= X-Received: by 2002:a7b:c444:: with SMTP id l4mr16519573wmi.15.1558698192747; Fri, 24 May 2019 04:43:12 -0700 (PDT) Received: from localhost (nat-pool-brq-t.redhat.com. [213.175.37.10]) by smtp.gmail.com with ESMTPSA id a128sm2210109wmc.13.2019.05.24.04.43.11 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 24 May 2019 04:43:11 -0700 (PDT) Date: Fri, 24 May 2019 13:43:10 +0200 From: Oleksandr Natalenko To: Justin Piszcz Cc: "Kirill A. Shutemov" , LKML Subject: Re: 5.1 kernel: khugepaged stuck at 100% Message-ID: <20190524114310.6h3tlslncepa6323@butterfly.localdomain> References: <002901d5064d$42355ea0$c6a01be0$@lucidpixels.com> <20190509111343.rvmy5noqlf4os3zk@box> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 16, 2019 at 10:27:50AM -0400, Justin Piszcz wrote: > On Thu, May 16, 2019 at 10:17 AM Justin Piszcz wrote: > > > > On Thu, May 16, 2019 at 10:14 AM Justin Piszcz wrote: > > > > > > On Tue, May 14, 2019 at 9:16 AM Kirill A. Shutemov wrote: > > > > > > > Could you check what khugepaged doing? > > > > > > > > cat /proc/$(pidof khugepaged)/stack > > > > > > It is doing it again, 10:12am - 2019-05-16 > > > > > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > > 77 root 39 19 0 0 0 R 100.0 0.0 92:06.94 khugepaged > > > > > > Kernel: 5.1.2 > > > > > > $ sudo cat /proc/$(pidof khugepaged)/stack > > > [<0>] 0xffffffffffffffff > > > > > As a workaround/in the meantime--I will add the following to lilo/grub: > transparent_hugepage=never > > Justin Cc'ing myself since i observe such a behaviour sometimes right after KVM VM is launched. No luck with reproducing it on demand so far, though. -- Best regards, Oleksandr Natalenko (post-factum) Senior Software Maintenance Engineer