Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 12 Jul 2022 12:54:24 +0100
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
Message-ID: <Ys1g8PH4M2W7Z50U@sirena.org.uk>
References: <CA+G9fYtOX-6=f70FA5PuDVA=kX=2L4spXKXS8=LHkUphafXowg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="Svukf3kgPdM45YjX"
Content-Disposition: inline
In-Reply-To: <CA+G9fYtOX-6=f70FA5PuDVA=kX=2L4spXKXS8=LHkUphafXowg@mail.gmail.com>
Precedence: bulk


--Svukf3kgPdM45YjX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 12, 2022 at 03:27:09PM +0530, Naresh Kamboju wrote:

> FVP boot failed with linux next 20220712.

I can't reproduce this, including with your kernel binary, which
suggests that this an issue with your FVP usage and firmware.

> Boot log:
> Starting kernel ...
>=20
> [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd0f0]
> [    0.000000] Linux version 5.19.0-rc6-next-20220711

How are you invoking the FVP, what firmware are you using and how is it
configured?

> [    0.500709] kernel BUG at arch/arm64/kernel/traps.c:497!

This is an undefined instruction, my first thought there would be that
you have some feature enabled for the kernel which requires enablement
at EL3 but your EL3 firmware is not configured to enable it.

> [    0.503562]  el1_undef+0x30/0x60
> [    0.503709]  el1h_64_sync_handler+0x84/0xd0
> [    0.503811]  el1h_64_sync+0x64/0x68
> [    0.503909]  net_sysctl_init+0x8/0x7c

This is where the undef came from.

--Svukf3kgPdM45YjX
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmLNYO8ACgkQJNaLcl1U
h9A6fAf/QTcF4jp1qJO2RoVPJc4OP7G1PJumqwmdm6mricWR87xdE7cbOZyK6pc7
G35LXMALDibQRhBd+tGJUQjAtka3IMIe0STZGVpbNp4H+1PyZASk3vLfgwtWVTMP
WQZt3HXC4ryTH/91yWSjDvJjoJkGRZlEStyqEgMUueBDUa6Cq5YuVlaKzFZW9VZ/
xbrs8tDLaFeI2uc6b1WkjldvDY8D3cahLxlkQ9myBuR2iDnr2ZvCmBiGzcpAAKAd
+/HYI0Z9mlXz/dlcwxeoSkYqB8Cny7EevAQSCNMzhl3rUKVJ29RsqmChXLiIWtWd
xOxOo0Nf1KT9hsIwn2GdAr3G/VSCGQ==
=/ii2
-----END PGP SIGNATURE-----

--Svukf3kgPdM45YjX--