linux-kernel - RE: [REGRESSION] Kernel reboots unexpectdely on i.MX8X when Cortex-M4 is running and it was started by U-Boot bootaux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <PAXPR04MB8459ED6CE869173D4051257088B62@PAXPR04MB8459.eurprd04.prod.outlook.com>
Date: Fri, 11 Apr 2025 13:23:32 +0000
From: Peng Fan <peng.fan@....com>
To: Hiago De Franco <hiagofranco@...il.com>, "linux-pm@...r.kernel.org"
	<linux-pm@...r.kernel.org>
CC: Ulf Hansson <ulf.hansson@...aro.org>, Shawn Guo <shawnguo@...nel.org>,
	Sascha Hauer <s.hauer@...gutronix.de>, "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "regressions@...ts.linux.dev"
	<regressions@...ts.linux.dev>, Hiago De Franco <hiago.franco@...adex.com>
Subject: RE: [REGRESSION] Kernel reboots unexpectdely on i.MX8X when Cortex-M4
 is running and it was started by U-Boot bootaux

Hi,

Sorry for late.
> Subject: Re: [REGRESSION] Kernel reboots unexpectdely on i.MX8X
> when Cortex-M4 is running and it was started by U-Boot bootaux
> 
> On Fri, Apr 04, 2025 at 11:17:13AM -0300, Hiago De Franco wrote:
> > #regzbot introduced: 4f6c983261
> >
> > Hi Peng and all,
> >
> > Commit 4f6c9832613b ("genpd: imx: scu-pd: initialize is_off
> according
> > to HW state") introduced a regression where the Kernel reboots
> > unexpectedly (without any warnings, crashes or errors) when the
> > Cortex-M4 was loaded and running by U-Boot, using the bootaux
> command:
> >
> > # load mmc 0:2 ${loadaddr} /home/root/hello_world.bin # bootaux
> > ${loadaddr} 0 # boot
> >
> > This is a simple hello world binary that prints a message into the
> > M40.UART0 pin (demo from NXP MCUXpresso).

Which release is this image from?

> >
> > Before this commit, everything worked as expected, Linux boots fine
> > and the HMP core keeps running and printing messages to the UART.
> > After the commit, the kernel reboots at the beggining of the boot
> > process. The only relevant message is printed by U-Boot after reset:
> >
> > "Reset cause: SCFW fault reset"
> >
> > This commit was bisectabled, the same device tree, u-boot version,
> and
> > SCFW versions were used. Reverting this commit fixes the issues.
> >
> > For testing purposes, I created the following patch which also fixes
> > the
> > issue:
> >
> > diff --git a/drivers/pmdomain/imx/scu-pd.c
> > b/drivers/pmdomain/imx/scu-pd.c index
> 38f3cdd21042..0477b3fb4991
> > 100644
> > --- a/drivers/pmdomain/imx/scu-pd.c
> > +++ b/drivers/pmdomain/imx/scu-pd.c
> > @@ -539,6 +539,9 @@ imx_scu_add_pm_domain(struct device
> *dev, int idx,
> >                 return NULL;
> >         }
> >
> > +       if (strstr("cm40", sc_pd->name) != NULL)
> > +               is_off = true;
> > +
> >         ret = pm_genpd_init(&sc_pd->pd, NULL, is_off);
> >         if (ret) {
> >                 dev_warn(dev, "failed to init pd %s rsrc id %d",
> >
> >
> > Test Environment:
> > - Hardware: Colibri iMX8DX 1GB with Colbiri Evaluation Board.
> > - U-Boot Version: 2024.04
> > - U-Boot Build info:
> > 	SCFW 83624b99, SECO-FW c9de51c0, IMX-MKIMAGE
> 4622115c, ATF 7c64d4e
> >
> > The issue is not present on: v6.5
> >
> > The real root cause is still unclear to me. Anybody has any ideas? I
> > am happy to share more details if needed.

Have you tried pd_ignore_unused? 

I think it is linux power down M4 which M4 is running, then SCFW
reports error. So please give a try pd_ignore_unused.

If this is the case, may I know do you have m4 nodes in dts and
with power domain included?

Anyway, I will give a try on i.MX8QM EVK.

> 
> Hello everyone, as this introduced a regression, should I send a revert
> for 4f6c983261? 

Please wait a while, I think we need find root cause.

Thanks,
Peng.

Or any ideas that might help fix this issue?
> 
> >
> > Cheers,
> > Hiago.
> 
> Cheers,
> Hiago.