Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c
From: Naresh Kamboju <hidden>
Date: 2021-06-17 12:15:51
Also in:
linux-mm, linux-next, lkml, regressions
Hi Will, On Tue, 15 Jun 2021 at 17:20, Will Deacon [off-list ref] wrote:
Hi Naresh, On Tue, Jun 15, 2021 at 04:41:25PM +0530, Naresh Kamboju wrote:quoted
Following kernel crash reported while boot linux next 20210615 tag on qemu_arm64 with allmodconfig build.
<trim>
Thanks for the report, although since this appears to be part of a broader
testing effort, here are some things that I think would make the reports
even more useful:
1. An indication as to whether or not this is a regression (i.e. do you
have a known good build, perhaps even a bisection?)
2. Either a link to the vmlinux, or faddr2line run on the backtrace.
Looking at the above, I can't tell what sparse_init_nid+0x98/0x6d0
actually is.
3. The exact QEMU command-line you are using, so I can try to reproduce
this locally. I think the 0-day bot wraps the repro up in a shell
script for you.
4. Whether or not the issue is reproducible.
5. Information about the toolchain you used to build the kernel (it
happens to be present here because it's in the kernel log, but
generally I think it would be handy to specify that in the report).
Please can you provide that information for this crash? It would really
help in debugging it.Sorry for the incomplete bug report. Thanks for sharing these details. Next time I will include the suggested data points in my email report. - Naresh _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel