Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp614388imu; Fri, 25 Jan 2019 07:58:55 -0800 (PST) X-Google-Smtp-Source: ALg8bN7+nT1wryEgyRbZVf68BTJTos/FyxjM0ng8bvEIvQ93KZGatBB8+q2Ko+1TGdwm/nn5HH5Y X-Received: by 2002:a17:902:bb98:: with SMTP id m24mr11200133pls.71.1548431934952; Fri, 25 Jan 2019 07:58:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548431934; cv=none; d=google.com; s=arc-20160816; b=lVQTLYiBYH7oaw6hQQj+Wx0/319CLLtT9KV3XamMTSBbLFC7DGyNdJdmfkgRG0TXsZ d5bPe2QXw1GMUCSugJls1cbmUusU5tE10DC0gqFHsL6phIW0bxppwL+NwqxF+ekkWprB 6WkE4B8Ri3oUZpNDJ/prM99zodT/WGKVsFs+sIkhEI/yi6wJkiDyNpfMvfa8CjktE2E3 J/OTfFbV1lcOqExH7fu/dKbQZFltCvc9SuSEeF6GCny+LskCWUZ4oSSxvZxsftOV/FL2 UwpxwMrC59+AY8DPzgpmiDmZMYf8CCA8Xvr9HYMIZ5XulYMrPDSx+lQqJEvLqzTu/zGx WgeQ== 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=+Fu+7MXvvMRvmae5O56DxhDhk41CfLakPO6k+iGJkrs=; b=cPeg+wPI9PMqroYdV2GqQENUvKPW+2JsvP1GtVcomh51c1xxD4CmAi1JGeRZaAONOy aDuiFeXQoUAbEeAq7SFdRy34hi1yeVZxyVPNSkGi14/v6XzVjiYPrMamhx3unBeGmSYh T8TlRaWyh3Mn6haKxI7P9HtZmhkR6LqHMEc9+Q4qhtPLIizA2J2tpXFwgtlUOd7rd+4s umHkq9tBZl9SGWtxR1E0RHl8OjoepIjWO5f0BR9+iXJXS8Csnd+BTlnqD/Jb6I7UzaAY 949iifyNwdWSe0zpFQ9qOhhZiZqXqS3paDEumuLjhnM4bXK/2VmT8WUxI0Dpd+hMckJ1 4KGw== 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v68si25064847pgb.70.2019.01.25.07.58.40; Fri, 25 Jan 2019 07:58:54 -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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729100AbfAYP6O (ORCPT + 99 others); Fri, 25 Jan 2019 10:58:14 -0500 Received: from mx2.suse.de ([195.135.220.15]:56634 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726321AbfAYP6O (ORCPT ); Fri, 25 Jan 2019 10:58:14 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 2EE8BAFE9; Fri, 25 Jan 2019 15:58:13 +0000 (UTC) Date: Fri, 25 Jan 2019 16:58:10 +0100 From: Michal Hocko To: robert shteynfeld Cc: Linus Torvalds , Mikhail Zaslonko , Linux List Kernel Mailing , Gerald Schaefer , Mikhail Gavrilov , Dave Hansen , Alexander Duyck , Andrew Morton , Pavel Tatashin , Steven Sistare , Daniel Jordan , Bob Picco Subject: Re: kernel panic due to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2830bf6f05fb3e05bc4743274b806c821807a684 Message-ID: <20190125155810.GQ3560@dhcp22.suse.cz> References: <20190125073704.GC3560@dhcp22.suse.cz> <20190125081924.GF3560@dhcp22.suse.cz> <20190125082952.GG3560@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 25-01-19 10:52:06, robert shteynfeld wrote: > The person who pointed to mm/page_alloc.c commits likely causing the > issue did not have time to build a patched/reverted kernel to confirm > his hypothesis. When I tried backing out the two separate commits he > suggested, the first commit (ie. the one in the subject) was the one > that when backed out fixed the boot issue. Reverting the second one > had no effect. OK, so can you provide the full dmesg (with revert) along wth memblock=debug kernel parameter. Also would it be possible to configure serial or net console to get the actual panic report please? -- Michal Hocko SUSE Labs