From: Jan Stancek <jstancek@redhat.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Zi Yan <ziy@nvidia.com>,
linux-mm@kvack.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Jonathan.Cameron@huawei.com, dan.j.williams@intel.com,
David Hildenbrand <david@redhat.com>,
linux-tegra@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: Re: [bug] aarch64 host no longer boots after 767507654c22 ("arch_numa: switch over to numa_memblks")
Date: Wed, 30 Oct 2024 22:50:12 +0100 [thread overview]
Message-ID: <CAASaF6xU4zbjFNEZkNLsPZz=d2-8dqbKkogU7xH05rgvUE4nhg@mail.gmail.com> (raw)
In-Reply-To: <ZyIvxWghfaK81I4d@kernel.org>
On Wed, Oct 30, 2024 at 2:12 PM Mike Rapoport <rppt@kernel.org> wrote:
>
> On Tue, Oct 29, 2024 at 10:03:31PM +0100, Jan Stancek wrote:
> > On Tue, Oct 29, 2024 at 5:24 PM Mike Rapoport <rppt@kernel.org> wrote:
> > >
> > > On Tue, Oct 29, 2024 at 04:43:39PM +0100, Jan Stancek wrote:
> > > > On Tue, Oct 29, 2024 at 4:07 PM Zi Yan <ziy@nvidia.com> wrote:
> > > > >
> > > > > +tegra mailing list and maintainers
> > > > >
> > > > > On 29 Oct 2024, at 8:47, Jan Stancek wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'm seeing a regression on Nvidia IGX system, which no longer boots.
> > > > > >
> > > > > > bisect points at commit 767507654c22 ("arch_numa: switch over to numa_memblks").
> > > > > > It hangs very early, with 4k or 64k pages, with no kernel messages printed:
> > > > > >
> > > > > > EFI stub: Booting Linux Kernel...
> > > > > > EFI stub: Using DTB from configuration table
> > > > > > EFI stub: Exiting boot services...
> > > > > > <hangs here>
> > > > > >
> > > > >
> > > > > Is it possible to have earlycon output? It is hard to debug without any
> > > > > information except kernel fails to boot.
> > > >
> > > > I know it was a long shot, so far I haven't had luck getting it to work.
> > >
> > > Does it boot with numa=off and numa=fake?
> >
> > No, it doesn't.
>
> No ideas without the logs, sorry.
With some trial & error I narrowed it down, but as it turns out
the fix has already landed upstream today:
d95fb348f016 ("mm: numa_clear_kernel_node_hotplug: Add NUMA_NO_NODE
check for node id")
Regards,
Jan
prev parent reply other threads:[~2024-10-30 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 12:47 Jan Stancek
2024-10-29 15:07 ` Zi Yan
2024-10-29 15:43 ` Jan Stancek
2024-10-29 16:20 ` Mike Rapoport
2024-10-29 21:03 ` Jan Stancek
2024-10-30 13:08 ` Mike Rapoport
2024-10-30 21:50 ` Jan Stancek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAASaF6xU4zbjFNEZkNLsPZz=d2-8dqbKkogU7xH05rgvUE4nhg@mail.gmail.com' \
--to=jstancek@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox