Re: [PATCH] arm64: smp: distinguish secondary CPUs that hang after reaching head.S

On 7/24/2026 10:53 AM, Anshuman Khandual wrote:

On 24/07/26 10:16 AM, Naman Jain wrote:

quoted

On 7/23/2026 11:26 AM, Anshuman Khandual wrote:

quoted

On 23/07/26 8:19 AM, Jinjie Ruan wrote:

quoted

在 2026/7/22 19:30, Naman Jain 写道:

quoted

When a secondary CPU fails to come online, __cpu_up() falls back to
__early_cpu_boot_status, but boot status 0x0 is ambiguous: it cannot
distinguish a CPU that never executed head.S (firmware/hypervisor never
dispatched it, so it never ran a single instruction) from one that
entered head.S, started executing, and then got stuck somewhere in kernel
bring-up. Add a change to let us tell those two cases apart, which
narrows down where to look when a CPU goes missing during boot.

I previously encountered this issue when debugging the parallel startup
of ARM64 secondary cores. It is difficult for the kernel to determine
whether the secondary core is hung in the firmware or whether it has not
executed a single instruction. So I think this motive is reasonable.

Why should kernel determine the difference here ? Would not the firmware
know if it has started any secondary CPU for the kernel which must have
come inside head.S ? If the cpu gets hung inside firmware while starting
up then the debug responsibilities belong there instead.

Still wondering what's the rationale for this change.

Hello Anshuman,
This sounds fair to me. Let me elaborate the problem, beyond the scope of this patch. In production, we occasionally see these crashes where one of the CPU fails to bring up online, with 0x0 status code. Hypervisor may be missing the telemetry, but the problem is that we don't know if the secondary CPU ever started executing the instructions or is stuck somewhere between the start of head.S and marking itself online at the end of secondary_start_kernel().

Why that information is useful ? If firmware is sure to have dispatched
given CPU then should not the early kernel boot failure be debugged via
generally available methods. Is this trying create an alternative ?

I am trying to cover the cases, where the kernel does not know that it
is stuck, and can thus cannot handle that scenario. Existing
CPU_STUCK_IN_KERNEL status with CPU_STUCK_REASON_* are applied only
after the kernel detects that something failed.

Generally available methods, like adding breakpoints, debug logs and
traces, is not always possible due to production system limitations and
limited reproducibility of issues.

quoted

There are couple of places, where we get those other status codes, but not everywhere. If the issue is not easily reproducible, experiments on local setups do not yield anything. That's where I am attempting to add some more information in kernel to debug these issues.

But wondering if the intent is to further classify failures including
entered ASM, but failed else where during boot for ease in debugging
why not add more into CPU_STUCK_REASON_* ?

If we agree on the requirement for this, I can then reuse
CPU_STUCK_IN_KERNEL with new CPU_STUCK_REASON_* variables, to
proactively mark the CPU as STUCK first and then making checkpoints
based on the boot-up progress, and finally changing the status to
CPU_BOOT_SUCCESS as usual.
I would be adding these checkpoints only on a few logical blocks of
secondary CPU boot flow to narrow down the problem.

Please let me know your thoughts on it.

Regards,
Naman