[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YW7p3ARYbpxmeLCF@arm.com>
Date: Tue, 19 Oct 2021 16:53:00 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Qian Cai <quic_qiancai@...cinc.com>
Cc: Mike Rapoport <rppt@...nel.org>, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] memblock: exclude NOMAP regions from kmemleak
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
Powered by blists - more mailing lists