From: Naresh Kamboju <naresh.kamboju@linaro.org> To: Mark Brown <broonie@kernel.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 01:07:32 +0530 [thread overview] Message-ID: <CA+G9fYu7mJ6X3_xhboODP_cjABE4QTJCON_NMduQ60x4Z7N78Q@mail.gmail.com> (raw) In-Reply-To: <Ys1g8PH4M2W7Z50U@sirena.org.uk> On Tue, 12 Jul 2022 at 17:24, Mark Brown <broonie@kernel.org> wrote: > > 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 ... > > > > [ 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. Thanks for investigating the reported issue and providing details. We will do the needful to update / configure EL3 firmware. > > > [ 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. 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) 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 https://builds.tuxbuild.com/2BnQMpJj3kDTJXoCwd2pY5gW9CN/Image.gz https://builds.tuxbuild.com/2BnQMpJj3kDTJXoCwd2pY5gW9CN/modules.tar.xz docker run --rm --interactive --tty --hostname lava --name tuxrun-r4_1075p-lava-1 --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/url-repo-action-3h1oa_zl/url_repo/https___storage.tuxboot.com_test-definitions_2022.01.tar:/tuxrun-r4_1075p-lava-1/https___storage.tuxboot.com_test-definitions_2022.01.tar --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/bl1/tf-bl1.bin:/tuxrun-r4_1075p-lava-1/tf-bl1.bin --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/dtb/fvp-base-revc.dtb:/tuxrun-r4_1075p-lava-1/fvp-base-revc.dtb --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/fip/fip-uboot.bin:/tuxrun-r4_1075p-lava-1/fip-uboot.bin --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/kernel/Image:/tuxrun-r4_1075p-lava-1/Image --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/rootfs/https___storage.lkft.org_rootfs_oe-sumo_20220219_juno_rpb-console-image-lkft-juno-20220219023239.rootfs.ext4:/tuxrun-r4_1075p-lava-1/https___storage.lkft.org_rootfs_oe-sumo_20220219_juno_rpb-console-image-lkft-juno-20220219023239.rootfs.ext4 --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/rootfs.modules/modules.tar:/tuxrun-r4_1075p-lava-1/modules.tar fvp:aemva-11.17.21 /opt/model/FVP_AEMvA/models/Linux64_GCC-9.3/FVP_Base_RevC-2xAEMvA --plugin /opt/model/FVP_AEMvA/plugins/Linux64_GCC-9.3/ScalableVectorExtension.so --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 -C cluster0.NUM_CORES=4 -C cluster1.NUM_CORES=4 -C cache_state_modelled=0 -C bp.smsc_91c111.enabled=true -C bp.pl011_uart0.untimed_fifos=1 -C bp.pl011_uart0.unbuffered_output=1 -C bp.secureflashloader.fname='/tuxrun-r4_1075p-lava-1/tf-bl1.bin' -C bp.flashloader0.fname='/tuxrun-r4_1075p-lava-1/fip-uboot.bin' -C bp.ve_sysregs.mmbSiteDefault=0 -C bp.ve_sysregs.exit_on_shutdown=1 -C bp.virtioblockdevice.image_path='/tuxrun-r4_1075p-lava-1/https___storage.lkft.org_rootfs_oe-sumo_20220219_juno_rpb-console-image-lkft-juno-20220219023239.rootfs.ext4' -C pci.pcidevice0.bus=0xFF -C pci.pcidevice1.bus=0xFF -C cluster0.has_large_system_ext=1 -C cluster1.has_large_system_ext=1 -C cluster0.has_16k_granule=1 -C cluster1.has_16k_granule=1 -C cluster0.has_branch_target_exception=1 -C cluster1.has_branch_target_exception=1 -C cluster0.has_rndr=1 -C cluster1.has_rndr=1 -C cluster0.has_arm_v8-1=1 -C cluster1.has_arm_v8-1=1 -C cluster0.has_arm_v8-2=1 -C cluster1.has_arm_v8-2=1 -C cluster0.has_arm_v8-3=1 -C cluster1.has_arm_v8-3=1 -C cluster0.has_arm_v8-4=1 -C cluster1.has_arm_v8-4=1 -C cluster0.has_arm_v8-5=1 -C cluster1.has_arm_v8-5=1 -C cluster0.has_arm_v8-6=1 -C cluster1.has_arm_v8-6=1 - Naresh
WARNING: multiple messages have this Message-ID (diff)
From: Naresh Kamboju <naresh.kamboju@linaro.org> To: Mark Brown <broonie@kernel.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 01:07:32 +0530 [thread overview] Message-ID: <CA+G9fYu7mJ6X3_xhboODP_cjABE4QTJCON_NMduQ60x4Z7N78Q@mail.gmail.com> (raw) In-Reply-To: <Ys1g8PH4M2W7Z50U@sirena.org.uk> On Tue, 12 Jul 2022 at 17:24, Mark Brown <broonie@kernel.org> wrote: > > 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 ... > > > > [ 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. Thanks for investigating the reported issue and providing details. We will do the needful to update / configure EL3 firmware. > > > [ 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. 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) 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 https://builds.tuxbuild.com/2BnQMpJj3kDTJXoCwd2pY5gW9CN/Image.gz https://builds.tuxbuild.com/2BnQMpJj3kDTJXoCwd2pY5gW9CN/modules.tar.xz docker run --rm --interactive --tty --hostname lava --name tuxrun-r4_1075p-lava-1 --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/url-repo-action-3h1oa_zl/url_repo/https___storage.tuxboot.com_test-definitions_2022.01.tar:/tuxrun-r4_1075p-lava-1/https___storage.tuxboot.com_test-definitions_2022.01.tar --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/bl1/tf-bl1.bin:/tuxrun-r4_1075p-lava-1/tf-bl1.bin --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/dtb/fvp-base-revc.dtb:/tuxrun-r4_1075p-lava-1/fvp-base-revc.dtb --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/fip/fip-uboot.bin:/tuxrun-r4_1075p-lava-1/fip-uboot.bin --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/kernel/Image:/tuxrun-r4_1075p-lava-1/Image --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/rootfs/https___storage.lkft.org_rootfs_oe-sumo_20220219_juno_rpb-console-image-lkft-juno-20220219023239.rootfs.ext4:/tuxrun-r4_1075p-lava-1/https___storage.lkft.org_rootfs_oe-sumo_20220219_juno_rpb-console-image-lkft-juno-20220219023239.rootfs.ext4 --volume /var/lib/lava/dispatcher/tmp/tuxrun-r4_1075p-1/fvp-deploy-w_qt5qgt/rootfs.modules/modules.tar:/tuxrun-r4_1075p-lava-1/modules.tar fvp:aemva-11.17.21 /opt/model/FVP_AEMvA/models/Linux64_GCC-9.3/FVP_Base_RevC-2xAEMvA --plugin /opt/model/FVP_AEMvA/plugins/Linux64_GCC-9.3/ScalableVectorExtension.so --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 -C cluster0.NUM_CORES=4 -C cluster1.NUM_CORES=4 -C cache_state_modelled=0 -C bp.smsc_91c111.enabled=true -C bp.pl011_uart0.untimed_fifos=1 -C bp.pl011_uart0.unbuffered_output=1 -C bp.secureflashloader.fname='/tuxrun-r4_1075p-lava-1/tf-bl1.bin' -C bp.flashloader0.fname='/tuxrun-r4_1075p-lava-1/fip-uboot.bin' -C bp.ve_sysregs.mmbSiteDefault=0 -C bp.ve_sysregs.exit_on_shutdown=1 -C bp.virtioblockdevice.image_path='/tuxrun-r4_1075p-lava-1/https___storage.lkft.org_rootfs_oe-sumo_20220219_juno_rpb-console-image-lkft-juno-20220219023239.rootfs.ext4' -C pci.pcidevice0.bus=0xFF -C pci.pcidevice1.bus=0xFF -C cluster0.has_large_system_ext=1 -C cluster1.has_large_system_ext=1 -C cluster0.has_16k_granule=1 -C cluster1.has_16k_granule=1 -C cluster0.has_branch_target_exception=1 -C cluster1.has_branch_target_exception=1 -C cluster0.has_rndr=1 -C cluster1.has_rndr=1 -C cluster0.has_arm_v8-1=1 -C cluster1.has_arm_v8-1=1 -C cluster0.has_arm_v8-2=1 -C cluster1.has_arm_v8-2=1 -C cluster0.has_arm_v8-3=1 -C cluster1.has_arm_v8-3=1 -C cluster0.has_arm_v8-4=1 -C cluster1.has_arm_v8-4=1 -C cluster0.has_arm_v8-5=1 -C cluster1.has_arm_v8-5=1 -C cluster0.has_arm_v8-6=1 -C cluster1.has_arm_v8-6=1 - Naresh _______________________________________________ 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-13 19: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 [this message] 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 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=CA+G9fYu7mJ6X3_xhboODP_cjABE4QTJCON_NMduQ60x4Z7N78Q@mail.gmail.com \ --to=naresh.kamboju@linaro.org \ --cc=Aishwarya.TCV@arm.com \ --cc=anders.roxell@linaro.org \ --cc=arnd@arndb.de \ --cc=broonie@kernel.org \ --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=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: linkBe 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.