From: "Russell King (Oracle)" <linux@armlinux•org.uk>
To: Naresh Kamboju <naresh.kamboju@linaro•org>
Cc: Linux ARM <linux-arm-kernel@lists•infradead.org>,
open list <linux-kernel@vger•kernel.org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
lkft-triage@lists•linaro.org,
Stephen Rothwell <sfr@canb•auug.org.au>,
Arnd Bergmann <arnd@arndb•de>, Ard Biesheuvel <ardb@kernel•org>,
Andrew Morton <akpm@linux-foundation•org>,
max.krummenacher@toradex•com, Shawn Guo <shawnguo@kernel•org>,
Stefano Stabellini <stefano.stabellini@xilinx•com>,
Christoph Hellwig <hch@lst•de>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle•com>,
"Eric W. Biederman" <ebiederm@xmission•com>
Subject: Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
Date: Tue, 19 Apr 2022 19:57:38 +0100 [thread overview]
Message-ID: <Yl8GInPZyl2PqK7D@shell.armlinux.org.uk> (raw)
In-Reply-To: <CA+G9fYuACgY2hcAgh_LwVb9AURjodMJbV6SsJb90wj-0aJKUOw@mail.gmail.com>
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?
If so, nothing has changed in the ARM32 kernel tree, so this must be
someone else's issue - code that someone else has pushed into
linux-next.
It looks to me like someone is walking the page tables incorrectly,
somewhere buried in handle_mm_fault(), because the PTE pointer is in
the upper-2k of a 4k page, which is most definitely illegal on arm32.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-04-19 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 10:58 [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext Naresh Kamboju
2022-04-19 18:57 ` Russell King (Oracle) [this message]
2022-04-20 8:55 ` Naresh Kamboju
2022-04-20 9:44 ` Russell King (Oracle)
2022-04-20 7:31 ` Ard Biesheuvel
2022-04-20 7:50 ` Max Krummenacher
2022-04-20 13:04 ` Naresh Kamboju
2022-04-20 21:53 ` Andrew Morton
2022-04-20 8:54 ` Naresh Kamboju
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=Yl8GInPZyl2PqK7D@shell.armlinux.org.uk \
--to=linux@armlinux$(echo .)org.uk \
--cc=akpm@linux-foundation$(echo .)org \
--cc=ardb@kernel$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=ebiederm@xmission$(echo .)com \
--cc=hch@lst$(echo .)de \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=max.krummenacher@toradex$(echo .)com \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=shawnguo@kernel$(echo .)org \
--cc=stefano.stabellini@xilinx$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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