mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kepplinger-Novakovic Martin <Martin.Kepplinger-Novakovic@ginzinger.com>
To: "suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
	"mike.leach@arm.com" <mike.leach@arm.com>,
	"james.clark@linaro.org" <james.clark@linaro.org>,
	"leo.yan@arm.com" <leo.yan@arm.com>,
	"alexander.shishkin@linux.intel.com"
	<alexander.shishkin@linux.intel.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"coresight@lists.linaro.org" <coresight@lists.linaro.org>,
	Roosen Henri <Henri.Roosen@ginzinger.com>
Subject: [BUG] coresight: during reboot-loop-test, boot hangs during 1st us
Date: Thu, 19 Nov 2026 11:10:50 +0000	[thread overview]
Message-ID: <f3e3c30ef76310fb6fb7d00019a8ef11e91ee1e1.camel@ginzinger.com> (raw)

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!

[    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.

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'm happy to test a patch,

thank you,
                                      martin

                 reply	other threads:[~2026-11-19 11:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=f3e3c30ef76310fb6fb7d00019a8ef11e91ee1e1.camel@ginzinger.com \
    --to=martin.kepplinger-novakovic@ginzinger.com \
    --cc=Henri.Roosen@ginzinger.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=coresight@lists.linaro.org \
    --cc=james.clark@linaro.org \
    --cc=leo.yan@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.leach@arm.com \
    --cc=suzuki.poulose@arm.com \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®