Re: [BUG] coresight: during reboot-loop-test, boot hangs during 1st us
From: Leo Yan
Date: Thu Nov 19 2026 - 09:53:58 EST
Hi,
On Thu, Nov 19, 2026 at 11:10:50AM +0000, Kepplinger-Novakovic Martin wrote:
> hi Suzuki, Mike and others,
>
> I don't really know the coresight hardware but with CORESIGHT enabled, when I do
> "reboot tests" on imx8mp, I see the kernel hang after (randomly) 200 to 2000 (sometimes
> a hang was seen even later) reboots at *about* the line below. But indeed not exactly
> that line. sometimes it stops 4-7 lines earlier!
Could you enable earlycon together with ignore_loglevel and initcall_debug?
So far, the info is too limited to give any useful hints.
> [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
> [ 0.000000] Linux version 6.18.63-ge-26.10+-ge_bep4-eta-1-00195-gb8bebc692f96 (root@ginzinger) (aarch64-buildroot-linux-gnu-gcc.br_real (Buildroot
> -gf002287f) 13.4.0, GNU ld (GNU Binutils) 2.43.1) #41 SMP PREEMPT Thu Nov 12 09:08:03 CET 2026
> [ 0.000000] KASLR disabled due to lack of seed
> [ 0.000000] Machine model: BE-P4 i.MX8MPlus in NDM
> [ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000007fffffff]
> [ 0.000000] NODE_DATA(0) allocated [mem 0x7fdb6e80-0x7fdb9b7f]
> [ 0.000000] Zone ranges:
> [ 0.000000] DMA [mem 0x0000000040000000-0x000000007fffffff]
> [ 0.000000] DMA32 empty
> [ 0.000000] Normal empty
> [ 0.000000] Movable zone start for each node
> [ 0.000000] Early memory node ranges
> [ 0.000000] node 0: [mem 0x0000000040000000-0x000000007fffffff]
> [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000007fffffff]
> [ 0.000000] cma: Reserved 32 MiB at 0x000000007cc00000
> [ 0.000000] psci: probing for conduit method from DT.
> [ 0.000000] psci: PSCIv1.1 detected in firmware.
> [ 0.000000] psci: Using standard PSCI v0.2 function IDs
> [ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
>
> The kernel does not panic. It hangs. The problem goes away and it reboots indefinitely
> when I disable coresight in the config.
Could you confirm what exactly CoreSight modules have been enabled?
> I sometimes need to run an old v5.10-imx based kernel, where I've *not* reproduced
> this hang with coresight enabled.
>
> Was there a regression in mainline or does NXP have a fix in their tree? Have you see
> something like this before?
I am not aware of a CoreSight regression. I cannot comment on NXP
board as I don't have it.
As separate diagnostic tests, could you try clk_ignore_unused and
nohlt, one at a time, to see whether unused-clock disabling or
CPU idle affects reproduction?
Thanks,
Leo