All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: 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>,
	Mark Rutland <mark.rutland@arm.com>,
	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: Thu, 14 Jul 2022 12:37:01 +0100	[thread overview]
Message-ID: <Ys//3Vf7kNSfFsdE@sirena.org.uk> (raw)
In-Reply-To: <CA+G9fYu7mJ6X3_xhboODP_cjABE4QTJCON_NMduQ60x4Z7N78Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2133 bytes --]

On Thu, Jul 14, 2022 at 01:07:32AM +0530, Naresh Kamboju wrote:

> Here I am providing the available data.
> Let me know what I am missing here, so that I will update my setup.
> Thanks in advance.

> Fast Models 11.17.21 (Feb 16 2022)

11.18 was released since (not that it should make any difference to this
issue).

> https://storage.tuxboot.com/fvp-aemva/tf-bl1.bin
> https://storage.tuxboot.com/fvp-aemva/fvp-base-revc.dtb
> https://storage.tuxboot.com/fvp-aemva/fip-uboot.bin

Where did you get the TF-A and u-boot from - what versions are they and
how are they configured and built?  Especially TF-A, u-boot isn't likely
to cause any issues here since it isn't responsible for initialising the
higher ELs.

That said I do seem to be able to boot with those images on my system -
it looks like a debug build of TF-A 2.5 and a modified version of u-boot
2021.04.  There's newer releases of both, especially with TF-A I'd
recommend keeping up with new releases though it doesn't *immediately*
look like your issue here.

> https://builds.tuxbuild.com/2BnQMpJj3kDTJXoCwd2pY5gW9CN/Image.gz
> https://builds.tuxbuild.com/2BnQMpJj3kDTJXoCwd2pY5gW9CN/modules.tar.xz

>   --data cluster0.cpu0=/tuxrun-r4_1075p-lava-1/fvp-base-revc.dtb@0x86000000
>   --data cluster0.cpu0=/tuxrun-r4_1075p-lava-1/Image@0x80080000
>    -C pctl.startup=0.0.0.0
>    -C bp.secure_memory=0

You don't seem to have

	-C cluster0.mpidr_layout=1 
	-C cluster1.mpidr_layout=1 

though I would expect that the system wouldn't get as far as it was
without that, it doesn't seem to when I try testing here - it dies
running TF-A.

You might also want to turn on a few more options

	-C cluster0.has_fgt=1
	-C cluster1.has_fgt=1
	-C cluster0.memory_tagging_support_level=3
	-C cluster1.memory_tagging_support_level=3
	-C bp.dram_metadata.is_enabled=1 

to turn on fine grained traps and MTE, plus at least the newer model has
more base architecture extensions, though these shouldn't be the issue
here.  They don't seem to be (and shouldn't be) relevant here though.
FGT is an EL2 feature so it'd die earlier.

[-- 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: 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>,
	Mark Rutland <mark.rutland@arm.com>,
	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: Thu, 14 Jul 2022 12:37:01 +0100	[thread overview]
Message-ID: <Ys//3Vf7kNSfFsdE@sirena.org.uk> (raw)
In-Reply-To: <CA+G9fYu7mJ6X3_xhboODP_cjABE4QTJCON_NMduQ60x4Z7N78Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2133 bytes --]

On Thu, Jul 14, 2022 at 01:07:32AM +0530, Naresh Kamboju wrote:

> Here I am providing the available data.
> Let me know what I am missing here, so that I will update my setup.
> Thanks in advance.

> Fast Models 11.17.21 (Feb 16 2022)

11.18 was released since (not that it should make any difference to this
issue).

> https://storage.tuxboot.com/fvp-aemva/tf-bl1.bin
> https://storage.tuxboot.com/fvp-aemva/fvp-base-revc.dtb
> https://storage.tuxboot.com/fvp-aemva/fip-uboot.bin

Where did you get the TF-A and u-boot from - what versions are they and
how are they configured and built?  Especially TF-A, u-boot isn't likely
to cause any issues here since it isn't responsible for initialising the
higher ELs.

That said I do seem to be able to boot with those images on my system -
it looks like a debug build of TF-A 2.5 and a modified version of u-boot
2021.04.  There's newer releases of both, especially with TF-A I'd
recommend keeping up with new releases though it doesn't *immediately*
look like your issue here.

> https://builds.tuxbuild.com/2BnQMpJj3kDTJXoCwd2pY5gW9CN/Image.gz
> https://builds.tuxbuild.com/2BnQMpJj3kDTJXoCwd2pY5gW9CN/modules.tar.xz

>   --data cluster0.cpu0=/tuxrun-r4_1075p-lava-1/fvp-base-revc.dtb@0x86000000
>   --data cluster0.cpu0=/tuxrun-r4_1075p-lava-1/Image@0x80080000
>    -C pctl.startup=0.0.0.0
>    -C bp.secure_memory=0

You don't seem to have

	-C cluster0.mpidr_layout=1 
	-C cluster1.mpidr_layout=1 

though I would expect that the system wouldn't get as far as it was
without that, it doesn't seem to when I try testing here - it dies
running TF-A.

You might also want to turn on a few more options

	-C cluster0.has_fgt=1
	-C cluster1.has_fgt=1
	-C cluster0.memory_tagging_support_level=3
	-C cluster1.memory_tagging_support_level=3
	-C bp.dram_metadata.is_enabled=1 

to turn on fine grained traps and MTE, plus at least the newer model has
more base architecture extensions, though these shouldn't be the issue
here.  They don't seem to be (and shouldn't be) relevant here though.
FGT is an EL2 feature so it'd die earlier.

[-- 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

  parent reply	other threads:[~2022-07-14 11:37 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
2022-07-15 12:28                   ` Mark Brown
2022-07-14 11:37     ` Mark Brown [this message]
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=Ys//3Vf7kNSfFsdE@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.