From: Naresh Kamboju <naresh.kamboju@linaro.org> To: Will Deacon <will@kernel.org> Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>, linux-mm <linux-mm@kvack.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, open list <linux-kernel@vger.kernel.org>, lkft-triage@lists.linaro.org, regressions@lists.linux.dev, Andrew Morton <akpm@linux-foundation.org>, Stephen Rothwell <sfr@canb.auug.org.au>, Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Mike Rapoport <rppt@linux.ibm.com>, Christophe Leroy <christophe.leroy@csgroup.eu> Subject: Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c Date: Thu, 17 Jun 2021 17:45:34 +0530 [thread overview] Message-ID: <CA+G9fYvCX5fd5dHdaGpQ7wpZNcea-=vtuhapW00D8AUkE5VUqA@mail.gmail.com> (raw) In-Reply-To: <20210615115044.GC20598@willie-the-truck> Hi Will, On Tue, 15 Jun 2021 at 17:20, Will Deacon <will@kernel.org> wrote: > > Hi Naresh, > > On Tue, Jun 15, 2021 at 04:41:25PM +0530, Naresh Kamboju wrote: > > 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
WARNING: multiple messages have this Message-ID (diff)
From: Naresh Kamboju <naresh.kamboju@linaro.org> To: Will Deacon <will@kernel.org> Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>, linux-mm <linux-mm@kvack.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, open list <linux-kernel@vger.kernel.org>, lkft-triage@lists.linaro.org, regressions@lists.linux.dev, Andrew Morton <akpm@linux-foundation.org>, Stephen Rothwell <sfr@canb.auug.org.au>, Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Mike Rapoport <rppt@linux.ibm.com>, Christophe Leroy <christophe.leroy@csgroup.eu> Subject: Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c Date: Thu, 17 Jun 2021 17:45:34 +0530 [thread overview] Message-ID: <CA+G9fYvCX5fd5dHdaGpQ7wpZNcea-=vtuhapW00D8AUkE5VUqA@mail.gmail.com> (raw) In-Reply-To: <20210615115044.GC20598@willie-the-truck> Hi Will, On Tue, 15 Jun 2021 at 17:20, Will Deacon <will@kernel.org> wrote: > > Hi Naresh, > > On Tue, Jun 15, 2021 at 04:41:25PM +0530, Naresh Kamboju wrote: > > 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
next prev parent reply other threads:[~2021-06-17 12:15 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-15 11:11 [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c Naresh Kamboju 2021-06-15 11:11 ` Naresh Kamboju 2021-06-15 11:11 ` Naresh Kamboju 2021-06-15 11:50 ` Will Deacon 2021-06-15 11:50 ` Will Deacon 2021-06-17 12:15 ` Naresh Kamboju [this message] 2021-06-17 12:15 ` Naresh Kamboju 2021-06-17 12:15 ` Naresh Kamboju 2021-06-15 12:47 ` Mark Rutland 2021-06-15 12:47 ` Mark Rutland 2021-06-15 13:19 ` Mark Rutland 2021-06-15 13:19 ` Mark Rutland 2021-06-15 14:50 ` Qian Cai 2021-06-15 14:50 ` Qian Cai 2021-06-15 19:21 ` Mike Rapoport 2021-06-15 19:21 ` Mike Rapoport 2021-06-15 23:34 ` Stephen Rothwell 2021-06-15 23:34 ` Stephen Rothwell 2021-06-15 23:40 ` Miles Chen 2021-06-15 23:40 ` Miles Chen 2021-06-16 0:29 ` Miles Chen 2021-06-16 0:29 ` Miles Chen
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='CA+G9fYvCX5fd5dHdaGpQ7wpZNcea-=vtuhapW00D8AUkE5VUqA@mail.gmail.com' \ --to=naresh.kamboju@linaro.org \ --cc=akpm@linux-foundation.org \ --cc=ardb@kernel.org \ --cc=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=christophe.leroy@csgroup.eu \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-next@vger.kernel.org \ --cc=lkft-triage@lists.linaro.org \ --cc=regressions@lists.linux.dev \ --cc=rppt@linux.ibm.com \ --cc=sfr@canb.auug.org.au \ --cc=will@kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.