From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org, regressions@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Aishwarya TCV <Aishwarya.TCV@arm.com>
Subject: Re: FVP: kernel BUG at arch/arm64/kernel/traps.c:497 - Internal error: Oops - BUG: 0
Date: Tue, 12 Jul 2022 13:52:55 +0100 [thread overview]
Message-ID: <Ys1up5DBGV5c2MG0@sirena.org.uk> (raw)
In-Reply-To: <Ys1t8win0pVPPuig@FVFF77S0Q05N.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
On Tue, Jul 12, 2022 at 01:49:55PM +0100, Mark Rutland wrote:
> ... and it boots perfectly fine under:
> * An FVP Base RevC model using the latest boot-wrapper
Also with TF-A and u-boot (both some random recentish tip of tree
whenever I last built them).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-12 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 9:57 FVP: kernel BUG at arch/arm64/kernel/traps.c:497 - Internal error: Oops - BUG: 0 Naresh Kamboju
2022-07-12 11:54 ` Mark Brown
2022-07-13 19:37 ` Naresh Kamboju
2022-07-14 11:26 ` Mark Rutland
2022-07-14 11:42 ` Mark Brown
2022-07-14 12:57 ` Mark Rutland
2022-07-14 13:06 ` Mark Rutland
2022-07-14 13:39 ` Mark Rutland
2022-07-14 14:05 ` Naresh Kamboju
2022-07-15 12:28 ` Mark Brown
2022-07-14 11:37 ` Mark Brown
2022-07-12 12:49 ` Mark Rutland
2022-07-12 12:52 ` Mark Brown [this message]
2022-07-12 16:21 ` Mark Rutland
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=Ys1up5DBGV5c2MG0@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Aishwarya.TCV@arm.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mark.rutland@arm.com \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--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: link
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