On Mon, Jun 6, 2022 at 11:36 PM Shakeel Butt <shakeelb@xxxxxxxxxx> wrote: > > On Mon, Jun 6, 2022 at 11:25 PM Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > > > > Hi Naresh, > > > > On Tue, 7 Jun 2022 11:00:39 +0530 Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: > > > > > > On Mon, 6 Jun 2022 at 17:16, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: > > > > > > > > Linux next-20220606 arm64 boot failed. The kernel boot log is empty. > > > > I am bisecting this problem. > > > > > > > > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx> > > > > > > > > The initial investigation show that, > > > > > > > > GOOD: next-20220603 > > > > BAD: next-20220606 > > > > > > > > Boot log: > > > > Starting kernel ... > > > > > > Linux next-20220606 and next-20220607 arm64 boot failed. > > > The kernel panic log showing after earlycon. > > > > > > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx> > > > > Can you test v5.19-rc1, please? If that does not fail, then you could > > bisect between that and next-20220606 ... > > > > This is already reported at > https://lore.kernel.org/all/Yp4F6n2Ie32re7Ed@qian/ and I think we know > the underlying issue (which is calling virt_to_page() on a vmalloc > address). Sorry, I might be wrong. Just checked the stacktrace again and it seems like the failure is happening in early boot in this report. Though the error "Unable to handle kernel paging request at virtual address" is happening in the function mem_cgroup_from_obj(). Naresh, can you repro the issue if you revert the patch "net: set proper memcg for net_init hooks allocations"?
