Hi,
On Thu, Oct 31, 2024 at 02:10:14PM +0530, Naresh Kamboju wrote:
The QEMU-ARM64 boot has failed with the Linux next-20241031 tag. The boot log shows warnings at clockevents_register_device and followed by rcu_preempt detected stalls.
However, the system did not proceed far enough to reach the login prompt. The fvp-aemva, Qemu-arm64, Qemu-armv7 and Qemu-riscv64 boot failed.
Please find the incomplete boot log links below for your reference. The Qemu version is 9.0.2.
This is always reproducible. First seen on Linux next-20241031 tag. Good: next-20241030 Good: next-20241031
qemu-arm64: boot: * clang-19-lkftconfig * gcc-13-lkftconfig * clang-nightly-lkftconfig
qemu-armv7: boot: * clang-19-lkftconfig * gcc-13-lkftconfig * clang-nightly-lkftconfig
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
Boot log:
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x000f0510] 0.000000] Linux version 6.12.0-rc5-next-20241031 (tuxmake@tuxmake) (aarch64-linux-gnu-gcc (Debian 13.3.0-5) 13.3.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP PREEMPT @1730356841 [ 0.000000] KASLR enabled [ 0.000000] random: crng init done [ 0.000000] Machine model: linux,dummy-virt
<trim> <6>[ 0.216503] GICv3: CPU1: found redistributor 1 region 0:0x00000000080c0000 <6>[ 0.218511] GICv3: CPU1: using allocated LPI pending table @0x0000000100250000 <4>[ 0.220528] ------------[ cut here ]------------ <4>[ 0.220657] WARNING: CPU: 1 PID: 0 at kernel/time/clockevents.c:455 clockevents_register_device (kernel/time/clockevents.c:455
It's possible that I messed up something with clockevents.
Can you try to reproduce with:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core
And if so it's possible that the bad commit is somewhere between:
17a8945f369c (clockevents: Improve clockevents_notify_released() comment)
and
bf9a001fb8e4 (clocksource/drivers/timer-tegra: Remove clockevents shutdown call on offlining)
I wish I could reproduce on my own but I don't have easy access to such hardware.
Thanks.