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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5B4E9C433F5 for ; Tue, 19 Oct 2021 15:53:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3CA2461355 for ; Tue, 19 Oct 2021 15:53:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232726AbhJSPza (ORCPT ); Tue, 19 Oct 2021 11:55:30 -0400 Received: from mail.kernel.org ([198.145.29.99]:35222 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232797AbhJSPzS (ORCPT ); Tue, 19 Oct 2021 11:55:18 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 0F498610E7; Tue, 19 Oct 2021 15:53:03 +0000 (UTC) Date: Tue, 19 Oct 2021 16:53:00 +0100 From: Catalin Marinas To: Qian Cai Cc: Mike Rapoport , linux-mm@kvack.org, Andrew Morton , Mike Rapoport , Vladimir Zapolskiy , linux-kernel@vger.kernel.org, Linus Torvalds Subject: Re: [PATCH] memblock: exclude NOMAP regions from kmemleak Message-ID: References: <20211013054756.12177-1-rppt@kernel.org> <089478ad-3755-b085-d9aa-c68e9792895c@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <089478ad-3755-b085-d9aa-c68e9792895c@quicinc.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 19, 2021 at 11:06:11AM -0400, Qian Cai wrote: > On 10/19/2021 7:37 AM, Catalin Marinas wrote: > >>> I could help to confirm if it hangs right in the early boot somewhere if needed. > >> > >> The kernel config and a log of working kernel would help to start with. > > http://lsbug.org/tmp/ Thanks. I guess the log here is with the Mike's patch reverted. > > I don't think there's much in the log other than the EFI stub above. > > > >>> start_kernel() > >>> setup_arch() > >>> paging_init() > >>> map_mem() > >>> memblock_mark_nomap( > > > > Is this actual trace? It would be good to know where exactly it got > > stuck. > > No, I did not confirm anything yet. There is going to take a while to > figure out the exactly location that hang since even the early console > was not initialized yet. Any suggestion on how to debug in this case? Try "earlycon=pl011,mmio32,0x12600000" on the kernel command line and hopefully we get some early log. -- Catalin