[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYvRdg6t6OnoJy62Vte5XnSymyL6B6kARC_1Jao52h6ZYg@mail.gmail.com>
Date: Wed, 20 Apr 2022 14:25:32 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Arnd Bergmann <arnd@...db.de>,
Ard Biesheuvel <ardb@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
max.krummenacher@...adex.com, Shawn Guo <shawnguo@...nel.org>,
Stefano Stabellini <stefano.stabellini@...inx.com>,
Christoph Hellwig <hch@....de>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
On Wed, 20 Apr 2022 at 00:28, Russell King (Oracle)
<linux@...linux.org.uk> wrote:
>
> On Tue, Apr 19, 2022 at 04:28:52PM +0530, Naresh Kamboju wrote:
> > Linux next 20220419 boot failed on arm architecture qemu_arm and BeagleBoard
> > x15 device.
>
> Was the immediately previous linux-next behaving correctly?
This crash started happening from the next-20220413 tag.
- Naresh
Powered by blists - more mailing lists