[REGRESSION] Raspberry Pi 5 (BCM2712) hangs at boot since d87773de9efe (arm_arch_timer: default to EL2 virtual timer under VHE)
Marc Zyngier
maz at kernel.org
Mon Jul 6 07:40:49 PDT 2026
On Mon, 06 Jul 2026 15:13:27 +0100,
John <therealgraysky at proton.me> wrote:
>
> Since commit d87773de9efe ("clocksource/drivers/arm_arch_timer: Default to EL2 virtual timer when running VHE"), the Raspberry Pi 5 (BCM2712, arm64) hangs during boot on v7.2-rc1 and later. Reverting that commit on top of v7.2-rc2 boots reliably. Found by bisection.
>
> Environment: - Raspberry Pi 5 Model B, arm64, device-tree boot (no ACPI) - CPUs start at EL2 with VHE - Mainline v7.2-rc1 and v7.2-rc2
>
> Symptom: - Silent hang early in driver probe; no panic or oops. Boot banner shows
> "arch_timer: cp15 timer running at 54.00MHz (hyp-virt)". The first blocking, timer-backed wait during probe never returns because the EL2 virtual timer's interrupt is not delivered on this SoC, so clockevents are dead. The softlockup/hung-task detectors can't fire either, since they depend on the same dead timer.
>
Is that a guess? Or do you know something we don't? Or worse, is this
report entirely AI generated?
> Cause: - BCM2712's timer node lists five interrupts including the EL2 virtual
> timer (GIC PPI 12). The new default trusts that entry and switches to the EL2 virtual timer, whose interrupt is non-functional on this board. Before the commit, VHE systems used the EL2 physical timer, which works.
>
Again, how do you know it isn't functional? Could it be, for example,
that the firmware has not configured the interrupt correctly?
> Possible fix / workaround: - Removing the EL2 virtual-timer interrupt (GIC PPI 12) from the BCM2712
> timer node makes the driver fall back to the EL2 physical timer (the pre-commit behavior) and boots. Whether the correct fix is in the DT or in hardening the driver's PPI selection, I'll leave to you.
>
> #regzbot introduced: d87773de9efe1df6fe2ba379926f9df92f1a5913
A proposed fix has been posted at [1]. Until we hear from the
implementer about the state of the HW, it is difficult to do anything.
M.
[1] https://lore.kernel.org/all/878q898ulx.wl-maz@kernel.org/
--
Without deviation from the norm, progress is not possible.
More information about the linux-arm-kernel
mailing list