From: Mark Brown <broonie@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
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: Fri, 15 Jul 2022 13:28:26 +0100 [thread overview]
Message-ID: <YtFdarmJKQbV2Wz8@sirena.org.uk> (raw)
In-Reply-To: <CA+G9fYvmrraS7ANdRA0XDoM-u-oVvcHFWsrFuBya9Es_WN3fkw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
On Thu, Jul 14, 2022 at 07:35:50PM +0530, Naresh Kamboju wrote:
> On Thu, 14 Jul 2022 at 19:09, Mark Rutland <mark.rutland@arm.com> wrote:
> > When *only* using the initial loading into memory, that blows up in stackdepot
> > and with a subsequent bogus pointer dereference (full log below), and when
> > loaded via semihosting that just works. Note that my kernel is based on the
> > arm64 for-next/core branch, which itself is based on v5.19-rc3.
> > Naresh, please can you fix your boot flow before reporting any further issues?
>
> Yes.
If you don't *need* to use u-boot for any reason then it might be worth
looking into using EDK2 instead, it will dynamically place loaded images
so you don't need to worry about size issues unless you actually run out
of memory which is a whole other problem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
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: Fri, 15 Jul 2022 13:28:26 +0100 [thread overview]
Message-ID: <YtFdarmJKQbV2Wz8@sirena.org.uk> (raw)
In-Reply-To: <CA+G9fYvmrraS7ANdRA0XDoM-u-oVvcHFWsrFuBya9Es_WN3fkw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 821 bytes --]
On Thu, Jul 14, 2022 at 07:35:50PM +0530, Naresh Kamboju wrote:
> On Thu, 14 Jul 2022 at 19:09, Mark Rutland <mark.rutland@arm.com> wrote:
> > When *only* using the initial loading into memory, that blows up in stackdepot
> > and with a subsequent bogus pointer dereference (full log below), and when
> > loaded via semihosting that just works. Note that my kernel is based on the
> > arm64 for-next/core branch, which itself is based on v5.19-rc3.
> > Naresh, please can you fix your boot flow before reporting any further issues?
>
> Yes.
If you don't *need* to use u-boot for any reason then it might be worth
looking into using EDK2 instead, it will dynamically place loaded images
so you don't need to worry about size issues unless you actually run out
of memory which is a whole other problem.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2022-07-15 12:28 UTC|newest]
Thread overview: 28+ 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 9:57 ` Naresh Kamboju
2022-07-12 11:54 ` Mark Brown
2022-07-12 11:54 ` Mark Brown
2022-07-13 19:37 ` Naresh Kamboju
2022-07-13 19:37 ` Naresh Kamboju
2022-07-14 11:26 ` Mark Rutland
2022-07-14 11:26 ` Mark Rutland
2022-07-14 11:42 ` Mark Brown
2022-07-14 11:42 ` Mark Brown
2022-07-14 12:57 ` Mark Rutland
2022-07-14 12:57 ` Mark Rutland
2022-07-14 13:06 ` Mark Rutland
2022-07-14 13:06 ` Mark Rutland
2022-07-14 13:39 ` Mark Rutland
2022-07-14 13:39 ` Mark Rutland
2022-07-14 14:05 ` Naresh Kamboju
2022-07-14 14:05 ` Naresh Kamboju
2022-07-15 12:28 ` Mark Brown [this message]
2022-07-15 12:28 ` Mark Brown
2022-07-14 11:37 ` Mark Brown
2022-07-14 11:37 ` Mark Brown
2022-07-12 12:49 ` Mark Rutland
2022-07-12 12:49 ` Mark Rutland
2022-07-12 12:52 ` Mark Brown
2022-07-12 12:52 ` Mark Brown
2022-07-12 16:21 ` Mark Rutland
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=YtFdarmJKQbV2Wz8@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 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.