Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Bjorn Helgaas]

[+cc Sherry, author of 610fa91d9863, Richard, Mani, linux-pci]

On Mon, Jun 29, 2026 at 11:34:32AM -0300, Leonardo Costa wrote:
> Hello,
> 
> We are seeing a regression on Apalis iMX6 where the kernel doesn't boot in the
> newest v7.2-rc1 (it was working before, in v7.1). The device tree being used is the imx6q-apalis-eval.dtb. The kernel
> configuration used is the one shown below:
> 
>     https://gist.github.com/lcosta37/53efdb2fb6e6e0fc05437c7e53b47737
> 
> The kernel logs stop almost immediately as the board starts to boot, and I 
> don't notice any difference in the logs that points to the cause.
> 
> Is this known? We are seeing this behavior on all Apalis iMX6 modules, though
> we don't see it on Colibri iMX6, so it is not SoC-specific.

This regression is listed on
https://linux-regtracking.leemhuis.info/regzbot/mainline/ as being
caused by
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=master&id=610fa91d9863
("PCI: imx6: Assert PERST# before enabling regulators") but I can't
find any bisect or other report that specifically points to
610fa91d9863.

Can somebody confirm that reverting 610fa91d9863 fixes this
regression, or at least that 610fa91d9863^ works and 610fa91d9863
fails?

Bjorn

RE: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Hongxing Zhu (OSS)]

> -----Original Message-----
> From: Bjorn Helgaas <helgaas@kernel.org>
> Sent: Thursday, July 16, 2026 7:48 AM
> To: Leonardo Costa <leoreis.costa@gmail.com>
> Cc: robh@kernel.org; krzk+dt@kernel.org; conor+dt@kernel.org; Frank Li
> <frank.li@nxp.com>; s.hauer@pengutronix.de; kernel@pengutronix.de;
> festevam@gmail.com; leonardo.costa@toradex.com;
> devicetree@vger.kernel.org; imx@lists.linux.dev; linux-arm-
> kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> regressions@lists.linux.dev; Sherry Sun <sherry.sun@nxp.com>; Manivannan
> Sadhasivam <mani@kernel.org>; Hongxing Zhu <hongxing.zhu@nxp.com>; linux-
> pci@vger.kernel.org
> Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots
>
> [+cc Sherry, author of 610fa91d9863, Richard, Mani, linux-pci]
>
> On Mon, Jun 29, 2026 at 11:34:32AM -0300, Leonardo Costa wrote:
> > Hello,
> >
> > We are seeing a regression on Apalis iMX6 where the kernel doesn't
> > boot in the newest v7.2-rc1 (it was working before, in v7.1). The
> > device tree being used is the imx6q-apalis-eval.dtb. The kernel configuration
> used is the one shown below:
> >
> >
> > https://gist/
> > .github.com%2Flcosta37%2F53efdb2fb6e6e0fc05437c7e53b47737&data=05%7
> C02
> > %7Chongxing.zhu%40nxp.com%7C3d58575d22384d61d15608dee2cb7471%7C
> 686ea1d
> >
> 3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C639197560620871110%7CUnknow
> n%7CTWF
> >
> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMi
> IsI
> >
> kFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=KtTOaEVJI3aq6Bt
> V7Js
> > Y7r%2F9B5LY%2F%2BVj3xEMk592ghk%3D&reserved=0
> >
> > The kernel logs stop almost immediately as the board starts to boot,
> > and I don't notice any difference in the logs that points to the cause.
> >
> > Is this known? We are seeing this behavior on all Apalis iMX6 modules,
> > though we don't see it on Colibri iMX6, so it is not SoC-specific.
>
> This regression is listed on
> https://linux-/
> regtracking.leemhuis.info%2Fregzbot%2Fmainline%2F&data=05%7C02%7Chongx
> ing.zhu%40nxp.com%7C3d58575d22384d61d15608dee2cb7471%7C686ea1d3bc
> 2b4c6fa92cd99c5c301635%7C0%7C0%7C639197560620886501%7CUnknown%
> 7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa
> W4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=K%2FBs
> xg56w4Jv4Phf%2B7i4CePTQA1M45xNH%2BxcrjuA4r0%3D&reserved=0 as being
> caused by
> https://git.kernel/.
> org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git%2Fcommit
> %2F%3Fh%3Dmaster%26id%3D610fa91d9863&data=05%7C02%7Chongxing.zhu
> %40nxp.com%7C3d58575d22384d61d15608dee2cb7471%7C686ea1d3bc2b4c6f
> a92cd99c5c301635%7C0%7C0%7C639197560620895764%7CUnknown%7CTWF
> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMi
> IsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ZT0p2CaXc8EJ
> YM2mlEAJegvmDqObaa%2FFiZtbCvM3PHw%3D&reserved=0
> ("PCI: imx6: Assert PERST# before enabling regulators") but I can't find any bisect
> or other report that specifically points to 610fa91d9863.
>
> Can somebody confirm that reverting 610fa91d9863 fixes this regression, or at
> least that 610fa91d9863^ works and 610fa91d9863 fails?
Sorry for this severe regression. I have posted a fix that has been tested on
my i.MX6Q SabreSD board:

https://lore.kernel.org/imx/20260708035928.580236-2-hongxing.zhu@oss.nxp.com/

Hi Leonardo,

Would you be able to test this patch on your affected boards? Your testing
would help expedite the merge process and ensure the fix resolves the boot
issue you're experiencing.

Best Regards
Richard Zhu
>
> Bjorn

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Bjorn Helgaas]

On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
> > On Mon, Jun 29, 2026 at 11:34:32AM -0300, Leonardo Costa wrote:
> > > We are seeing a regression on Apalis iMX6 where the kernel
> > > doesn't boot in the newest v7.2-rc1 (it was working before, in
> > > v7.1). The device tree being used is the imx6q-apalis-eval.dtb.
> > > The kernel configuration
> > > used is the one shown below:
> ...

> > Can somebody confirm that reverting 610fa91d9863 fixes this
> > regression, or at least that 610fa91d9863^ works and 610fa91d9863
> > fails?
>
> Sorry for this severe regression. I have posted a fix that has been
> tested on my i.MX6Q SabreSD board:
> 
> https://lore.kernel.org/imx/20260708035928.580236-2-hongxing.zhu@oss.nxp.com/

My question was whether somebody had actually bisected to 610fa91d9863
("PCI: imx6: Assert PERST# before enabling regulators").  I don't see
anything specific on the mailing list, so I don't know how
610fa91d9863 got blamed for the regression.

https://linux-regtracking.leemhuis.info/regzbot/mainline/ lists this
as a regression caused by 610fa91d9863, which means we need (1) the
details to prove that 610fa91d9863 actually caused it and (2) a tested
revert or fix.

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Thorsten Leemhuis]

On 7/16/26 18:40, Bjorn Helgaas wrote:
> On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
>>> On Mon, Jun 29, 2026 at 11:34:32AM -0300, Leonardo Costa wrote:
>>>> We are seeing a regression on Apalis iMX6 where the kernel
>>>> doesn't boot in the newest v7.2-rc1 (it was working before, in
>>>> v7.1). The device tree being used is the imx6q-apalis-eval.dtb.
>>>> The kernel configuration
>>>> used is the one shown below:
>> ...
> 
>>> Can somebody confirm that reverting 610fa91d9863 fixes this
>>> regression, or at least that 610fa91d9863^ works and 610fa91d9863
>>> fails?
>>
>> Sorry for this severe regression. I have posted a fix that has been
>> tested on my i.MX6Q SabreSD board:
>>
>> https://lore.kernel.org/imx/20260708035928.580236-2-hongxing.zhu@oss.nxp.com/
> 
> My question was whether somebody had actually bisected to 610fa91d9863
> ("PCI: imx6: Assert PERST# before enabling regulators").  I don't see
> anything specific on the mailing list, so I don't know how
> 610fa91d9863 got blamed for the regression.

That was me and might have been a stupid idea. I normally wouldn't have
added this, but a earlier message from Hongxing Zhu sounded a pretty
convincingly like something along the lines of  "this is the problem I
already have a fix for there" -- and then I took the commit-id from there.

Sorry.

Ciao, Thorsten

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Bjorn Helgaas]

On Thu, Jul 16, 2026 at 07:16:31PM +0200, Thorsten Leemhuis wrote:
> On 7/16/26 18:40, Bjorn Helgaas wrote:
> > On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
> >>> On Mon, Jun 29, 2026 at 11:34:32AM -0300, Leonardo Costa wrote:
> >>>> We are seeing a regression on Apalis iMX6 where the kernel
> >>>> doesn't boot in the newest v7.2-rc1 (it was working before, in
> >>>> v7.1). The device tree being used is the imx6q-apalis-eval.dtb.
> >>>> The kernel configuration
> >>>> used is the one shown below:
> >> ...
> > 
> >>> Can somebody confirm that reverting 610fa91d9863 fixes this
> >>> regression, or at least that 610fa91d9863^ works and 610fa91d9863
> >>> fails?
> >>
> >> Sorry for this severe regression. I have posted a fix that has been
> >> tested on my i.MX6Q SabreSD board:
> >>
> >> https://lore.kernel.org/imx/20260708035928.580236-2-hongxing.zhu@oss.nxp.com/
> > 
> > My question was whether somebody had actually bisected to 610fa91d9863
> > ("PCI: imx6: Assert PERST# before enabling regulators").  I don't see
> > anything specific on the mailing list, so I don't know how
> > 610fa91d9863 got blamed for the regression.
> 
> That was me and might have been a stupid idea. I normally wouldn't have
> added this, but a earlier message from Hongxing Zhu sounded a pretty
> convincingly like something along the lines of  "this is the problem I
> already have a fix for there" -- and then I took the commit-id from there.

Ah, ok, that explains it, thanks!  Hopefully we can get some clear
connection in the patch that eventually gets merged.

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Leonardo Costa]

On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
> Hi Leonardo,
> 
> Would you be able to test this patch on your affected boards? Your testing
> would help expedite the merge process and ensure the fix resolves the boot
> issue you're experiencing.
> 
> Best Regards
> Richard Zhu

Hi Richard,

Sorry for taking long to respond, I was caught up with something. I
tested the patch and it solved the issue. I sent a Tested-by tag there.
Thanks for looking into this!

Best Regards
Leonardo

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Leonardo Costa]

On Thu, Jul 16, 2026 at 02:09:19PM -0300, Leonardo Costa wrote:
> On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
> > Hi Leonardo,
> > 
> > Would you be able to test this patch on your affected boards? Your testing
> > would help expedite the merge process and ensure the fix resolves the boot
> > issue you're experiencing.
> > 
> > Best Regards
> > Richard Zhu
> 
> Hi Richard,
> 
> Sorry for taking long to respond, I was caught up with something. I
> tested the patch and it solved the issue. I sent a Tested-by tag there.
> Thanks for looking into this!
> 
> Best Regards
> Leonardo

Hi Richard,

That patch might have introduced/exposed a second regression where PCI
devices are not linked properly during the initialization. Sorry for not 
catching this before, as I didn't have any device connected during the
previous test.

Link: https://lore.kernel.org/all/bl7i3obu2clzsgeoct2a4mtfhv6typcjdqmgneropf3hpgwve6@n2m5uhlduw57/T/#u

RE: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Hongxing Zhu (OSS)]

> -----Original Message-----
> From: Leonardo Costa <leoreis.costa@gmail.com>
> Sent: Tuesday, August 11, 2026 2:26 AM
> To: Hongxing Zhu (OSS) <hongxing.zhu@oss.nxp.com>
> Cc: Bjorn Helgaas <helgaas@kernel.org>; robh@kernel.org;
> krzk+dt@kernel.org; conor+dt@kernel.org; Frank Li <frank.li@nxp.com>;
> s.hauer@pengutronix.de; kernel@pengutronix.de; festevam@gmail.com;
> leonardo.costa@toradex.com; devicetree@vger.kernel.org;
> imx@lists.linux.dev; linux-arm-kernel@lists.infradead.org; linux-
> kernel@vger.kernel.org; regressions@lists.linux.dev; Sherry Sun
> <sherry.sun@nxp.com>; Manivannan Sadhasivam <mani@kernel.org>;
> Hongxing Zhu <hongxing.zhu@nxp.com>; linux-pci@vger.kernel.org
> Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots
> 
> On Thu, Jul 16, 2026 at 02:09:19PM -0300, Leonardo Costa wrote:
> > On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
> > > Hi Leonardo,
> > >
> > > Would you be able to test this patch on your affected boards? Your
> > > testing would help expedite the merge process and ensure the fix
> > > resolves the boot issue you're experiencing.
> > >
> > > Best Regards
> > > Richard Zhu
> >
> > Hi Richard,
> >
> > Sorry for taking long to respond, I was caught up with something. I
> > tested the patch and it solved the issue. I sent a Tested-by tag there.
> > Thanks for looking into this!
> >
> > Best Regards
> > Leonardo
> 
> Hi Richard,
> 
> That patch might have introduced/exposed a second regression where PCI
> devices are not linked properly during the initialization. Sorry for not catching
> this before, as I didn't have any device connected during the previous test.
Hi Leonardo:
Sorry to hear about that.
I did test commit 7678e81498e2 with one Intel NIC (82574L) connected, and I've
double-checked today based on v7.2-rc7. The PCIe link can be set up properly
on the i.MX6Q Sabresd board in my testing.

Here are the logs:
root@imx6qpdlsolox:~# lspci
00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
root@imx6qpdlsolox:~# uname -a
Linux imx6qpdlsolox 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
root@imx6qpdlsolox:~# dmesg | grep pci
[    0.256138] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
[    0.256307] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff -> 0x0000000000
[    0.256339] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -> 0x0001000000
[    0.256434] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu 0x01f00000
[    0.458388] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K, limit 4G
[    0.458492] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
[    0.555294] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
[    0.555783] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
...

The following endpoint devices also yielded the same results.
root@imx6qpdlsolox:~# lspci
00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
01:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
root@imx6qpdlsolox:~# uname -a
Linux imx6qpdlsolox 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
...

root@imx6qpdlsolox:~# lspci
00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
root@imx6qpdlsolox:~# uname -a
Linux imx6qpdlsolox 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux

Could you provide more details of your hardware setup (board, connected
devices, PERST# present or not)?
This may help us identify if there's a specific scenario that triggers the
regression you're experiencing.

Best Regards
Richard Zhu
> 
> Link:
> https://lore.kernel.org/all/bl7i3obu2clzsgeoct2a4mtfhv6typcjdqmgneropf3hp
> gwve6@n2m5uhlduw57/T/#u

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Francesco Dolcini]

On Tue, Aug 11, 2026 at 12:47:18AM +0000, Hongxing Zhu (OSS) wrote:
> > -----Original Message-----
> > From: Leonardo Costa <leoreis.costa@gmail.com>
> > Sent: Tuesday, August 11, 2026 2:26 AM
> > To: Hongxing Zhu (OSS) <hongxing.zhu@oss.nxp.com>
> > Cc: Bjorn Helgaas <helgaas@kernel.org>; robh@kernel.org;
> > krzk+dt@kernel.org; conor+dt@kernel.org; Frank Li <frank.li@nxp.com>;
> > s.hauer@pengutronix.de; kernel@pengutronix.de; festevam@gmail.com;
> > leonardo.costa@toradex.com; devicetree@vger.kernel.org;
> > imx@lists.linux.dev; linux-arm-kernel@lists.infradead.org; linux-
> > kernel@vger.kernel.org; regressions@lists.linux.dev; Sherry Sun
> > <sherry.sun@nxp.com>; Manivannan Sadhasivam <mani@kernel.org>;
> > Hongxing Zhu <hongxing.zhu@nxp.com>; linux-pci@vger.kernel.org
> > Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots
> > 
> > On Thu, Jul 16, 2026 at 02:09:19PM -0300, Leonardo Costa wrote:
> > > On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
> > > > Hi Leonardo,
> > > >
> > > > Would you be able to test this patch on your affected boards? Your
> > > > testing would help expedite the merge process and ensure the fix
> > > > resolves the boot issue you're experiencing.
> > > >
> > > > Best Regards
> > > > Richard Zhu
> > >
> > > Hi Richard,
> > >
> > > Sorry for taking long to respond, I was caught up with something. I
> > > tested the patch and it solved the issue. I sent a Tested-by tag there.
> > > Thanks for looking into this!
> > >
> > > Best Regards
> > > Leonardo
> > 
> > Hi Richard,
> > 
> > That patch might have introduced/exposed a second regression where PCI
> > devices are not linked properly during the initialization. Sorry for not catching
> > this before, as I didn't have any device connected during the previous test.
> Hi Leonardo:
> Sorry to hear about that.
> I did test commit 7678e81498e2 with one Intel NIC (82574L) connected, and I've
> double-checked today based on v7.2-rc7. The PCIe link can be set up properly
> on the i.MX6Q Sabresd board in my testing.
> 
> Here are the logs:
> root@imx6qpdlsolox:~# lspci
> 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> 01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
> root@imx6qpdlsolox:~# uname -a
> Linux imx6qpdlsolox 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
> root@imx6qpdlsolox:~# dmesg | grep pci
> [    0.256138] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> [    0.256307] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff -> 0x0000000000
> [    0.256339] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -> 0x0001000000
> [    0.256434] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu 0x01f00000
> [    0.458388] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K, limit 4G
> [    0.458492] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
> [    0.555294] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
> [    0.555783] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
> ...
> 
> The following endpoint devices also yielded the same results.
> root@imx6qpdlsolox:~# lspci
> 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> 01:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
> root@imx6qpdlsolox:~# uname -a
> Linux imx6qpdlsolox 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
> ...
> 
> root@imx6qpdlsolox:~# lspci
> 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> 01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
> root@imx6qpdlsolox:~# uname -a
> Linux imx6qpdlsolox 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
> 
> Could you provide more details of your hardware setup (board, connected
> devices, PERST# present or not)?
> This may help us identify if there's a specific scenario that triggers the
> regression you're experiencing.

It's an apalis imx6, as reported already in this email thread.
The DT is in Linux, you can check
arch/arm/boot/dts/nxp/imx/imx6q-apalis-ixora-v1.2.dts every details
about PERST# and more.

This is the device connected:

00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02)

01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
	Subsystem: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller
	Flags: bus master, fast devsel, latency 0, IRQ 308
	I/O ports at 1020 [size=8]
	I/O ports at 1030 [size=4]
	I/O ports at 1028 [size=8]
	I/O ports at 1034 [size=4]
	I/O ports at 1000 [size=32]
	Memory at 01100000 (32-bit, non-prefetchable) [size=512]
	Expansion ROM at 01200000 [virtual] [disabled] [size=64K]
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0
	Capabilities: [100] Virtual Channel
	Kernel driver in use: ahci
	Kernel modules: ahci


These are some working logs from a 6.6.151 kernel

[    0.233058] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
[    0.233112] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff -> 0x0000000000
[    0.233144] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -> 0x0001000000
[    0.465779] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K, limit 4G
[    0.564230] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
[    0.564249] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
[    0.564259] imx6q-pcie 1ffc000.pcie: Link up, Gen1
[    0.564272] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
[    0.564778] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
[    0.564795] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.564809] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
[    0.564821] pci_bus 0000:00: root bus resource [mem 0x01000000-0x01efffff]
[    0.564864] pci 0000:00:00.0: [16c3:abcd] type 01 class 0x060400
[    0.564886] pci 0000:00:00.0: BAR 0 [mem 0x00000000-0x000fffff]
[    0.564905] pci 0000:00:00.0: ROM [mem 0x00000000-0x0000ffff pref]
[    0.564917] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    0.564931] pci 0000:00:00.0:   bridge window [io  0x0000-0x0fff]
[    0.564943] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[    0.564957] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff pref]
[    0.565405] pci 0000:00:00.0: Limiting cfg_size to 512
[    0.565455] pci 0000:00:00.0: supports D1
[    0.565465] pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
[    0.574310] pci 0000:01:00.0: [1b21:0612] type 00 class 0x010601
[    0.574458] pci 0000:01:00.0: BAR 0 [io  0x0000-0x0007]
[    0.574541] pci 0000:01:00.0: BAR 1 [io  0x0000-0x0003]
[    0.574616] pci 0000:01:00.0: BAR 2 [io  0x0000-0x0007]
[    0.574774] pci 0000:01:00.0: BAR 3 [io  0x0000-0x0003]
[    0.574854] pci 0000:01:00.0: BAR 4 [io  0x0000-0x001f]
[    0.574925] pci 0000:01:00.0: BAR 5 [mem 0x00000000-0x000001ff]
[    0.575001] pci 0000:01:00.0: ROM [mem 0x00000000-0x0000ffff pref]
[    0.575765] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:00.0 (capable of 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
[    0.576808] pci 0000:00:00.0: BAR 0 [mem 0x01000000-0x010fffff]: assigned
[    0.576860] pci 0000:00:00.0: bridge window [mem 0x01100000-0x011fffff]: assigned
[    0.576895] pci 0000:00:00.0: bridge window [mem 0x01200000-0x012fffff pref]: assigned
[    0.576928] pci 0000:00:00.0: ROM [mem 0x01300000-0x0130ffff pref]: assigned
[    0.576958] pci 0000:00:00.0: bridge window [io  0x1000-0x1fff]: assigned
[    0.577000] pci 0000:01:00.0: ROM [mem 0x01200000-0x0120ffff pref]: assigned
[    0.577033] pci 0000:01:00.0: BAR 5 [mem 0x01100000-0x011001ff]: assigned
[    0.577087] pci 0000:01:00.0: BAR 4 [io  0x1000-0x101f]: assigned
[    0.577212] pci 0000:01:00.0: BAR 0 [io  0x1020-0x1027]: assigned
[    0.577273] pci 0000:01:00.0: BAR 2 [io  0x1028-0x102f]: assigned
[    0.577326] pci 0000:01:00.0: BAR 1 [io  0x1030-0x1033]: assigned
[    0.577377] pci 0000:01:00.0: BAR 3 [io  0x1034-0x1037]: assigned
[    0.577429] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    0.577460] pci 0000:00:00.0:   bridge window [io  0x1000-0x1fff]
[    0.577491] pci 0000:00:00.0:   bridge window [mem 0x01100000-0x011fffff]
[    0.577520] pci 0000:00:00.0:   bridge window [mem 0x01200000-0x012fffff pref]
[    0.579109] pcieport 0000:00:00.0: PME: Signaling with IRQ 291
[    0.580323] pcieport 0000:00:00.0: AER: enabled with IRQ 291

RE: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Hongxing Zhu]

NXP Confidential
> -----Original Message-----
> From: Francesco Dolcini <francesco@dolcini.it>
> Sent: Tuesday, August 11, 2026 2:38 PM
> To: Hongxing Zhu (OSS) <hongxing.zhu@oss.nxp.com>
> Cc: Leonardo Costa <leoreis.costa@gmail.com>; Bjorn Helgaas
> <helgaas@kernel.org>; robh@kernel.org; krzk+dt@kernel.org;
> conor+dt@kernel.org; Frank Li <frank.li@nxp.com>; s.hauer@pengutronix.de;
> kernel@pengutronix.de; festevam@gmail.com; leonardo.costa@toradex.com;
> devicetree@vger.kernel.org; imx@lists.linux.dev; linux-arm-
> kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> regressions@lists.linux.dev; Sherry Sun <sherry.sun@nxp.com>; Manivannan
> Sadhasivam <mani@kernel.org>; Hongxing Zhu <hongxing.zhu@nxp.com>;
> linux-pci@vger.kernel.org
> Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots
>
> On Tue, Aug 11, 2026 at 12:47:18AM +0000, Hongxing Zhu (OSS) wrote:
> > > -----Original Message-----
> > > From: Leonardo Costa <leoreis.costa@gmail.com>
> > > Sent: Tuesday, August 11, 2026 2:26 AM
> > > To: Hongxing Zhu (OSS) <hongxing.zhu@oss.nxp.com>
> > > Cc: Bjorn Helgaas <helgaas@kernel.org>; robh@kernel.org;
> > > krzk+dt@kernel.org; conor+dt@kernel.org; Frank Li
> > > krzk+<frank.li@nxp.com>;
> > > s.hauer@pengutronix.de; kernel@pengutronix.de; festevam@gmail.com;
> > > leonardo.costa@toradex.com; devicetree@vger.kernel.org;
> > > imx@lists.linux.dev; linux-arm-kernel@lists.infradead.org; linux-
> > > kernel@vger.kernel.org; regressions@lists.linux.dev; Sherry Sun
> > > <sherry.sun@nxp.com>; Manivannan Sadhasivam <mani@kernel.org>;
> > > Hongxing Zhu <hongxing.zhu@nxp.com>; linux-pci@vger.kernel.org
> > > Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer
> > > boots
> > >
> > > On Thu, Jul 16, 2026 at 02:09:19PM -0300, Leonardo Costa wrote:
> > > > On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
> > > > > Hi Leonardo,
> > > > >
> > > > > Would you be able to test this patch on your affected boards?
> > > > > Your testing would help expedite the merge process and ensure
> > > > > the fix resolves the boot issue you're experiencing.
> > > > >
> > > > > Best Regards
> > > > > Richard Zhu
> > > >
> > > > Hi Richard,
> > > >
> > > > Sorry for taking long to respond, I was caught up with something.
> > > > I tested the patch and it solved the issue. I sent a Tested-by tag there.
> > > > Thanks for looking into this!
> > > >
> > > > Best Regards
> > > > Leonardo
> > >
> > > Hi Richard,
> > >
> > > That patch might have introduced/exposed a second regression where
> > > PCI devices are not linked properly during the initialization. Sorry
> > > for not catching this before, as I didn't have any device connected during
> the previous test.
> > Hi Leonardo:
> > Sorry to hear about that.
> > I did test commit 7678e81498e2 with one Intel NIC (82574L) connected,
> > and I've double-checked today based on v7.2-rc7. The PCIe link can be
> > set up properly on the i.MX6Q Sabresd board in my testing.
> >
> > Here are the logs:
> > root@imx6qpdlsolox:~# lspci
> > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > 01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
> > Connection root@imx6qpdlsolox:~# uname -a Linux imx6qpdlsolox
> > 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
> > root@imx6qpdlsolox:~# dmesg | grep pci
> > [    0.256138] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> > [    0.256307] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff ->
> 0x0000000000
> > [    0.256339] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -
> > 0x0001000000
> > [    0.256434] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu
> 0x01f00000
> > [    0.458388] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K,
> limit 4G
> > [    0.458492] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
> > [    0.555294] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
> > [    0.555783] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
> > ...
> >
> > The following endpoint devices also yielded the same results.
> > root@imx6qpdlsolox:~# lspci
> > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > 01:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network
> > Adapter (PCI-Express) (rev 01) root@imx6qpdlsolox:~# uname -a Linux
> > imx6qpdlsolox 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l
> > GNU/Linux ...
> >
> > root@imx6qpdlsolox:~# lspci
> > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > 01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host
> > Controller (rev 04) root@imx6qpdlsolox:~# uname -a Linux imx6qpdlsolox
> > 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
> >
> > Could you provide more details of your hardware setup (board,
> > connected devices, PERST# present or not)?
> > This may help us identify if there's a specific scenario that triggers
> > the regression you're experiencing.
>
> It's an apalis imx6, as reported already in this email thread.
> The DT is in Linux, you can check
> arch/arm/boot/dts/nxp/imx/imx6q-apalis-ixora-v1.2.dts every details about
> PERST# and more.
>
> This is the device connected:
>
> 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> 01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial
> ATA Controller (rev 02)
>
> 01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial
> ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
>       Subsystem: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA
> Controller
>       Flags: bus master, fast devsel, latency 0, IRQ 308
>       I/O ports at 1020 [size=8]
>       I/O ports at 1030 [size=4]
>       I/O ports at 1028 [size=8]
>       I/O ports at 1034 [size=4]
>       I/O ports at 1000 [size=32]
>       Memory at 01100000 (32-bit, non-prefetchable) [size=512]
>       Expansion ROM at 01200000 [virtual] [disabled] [size=64K]
>       Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-
>       Capabilities: [78] Power Management version 3
>       Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0
>       Capabilities: [100] Virtual Channel
>       Kernel driver in use: ahci
>       Kernel modules: ahci
>
>
> These are some working logs from a 6.6.151 kernel
>
> [    0.233058] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> [    0.233112] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff ->
> 0x0000000000
> [    0.233144] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff ->
> 0x0001000000
> [    0.465779] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K, limit
> 4G
> [    0.564230] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
> [    0.564249] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
> [    0.564259] imx6q-pcie 1ffc000.pcie: Link up, Gen1
> [    0.564272] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
> [    0.564778] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
> [    0.564795] pci_bus 0000:00: root bus resource [bus 00-ff]
> [    0.564809] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
> [    0.564821] pci_bus 0000:00: root bus resource [mem 0x01000000-0x01efffff]
> [    0.564864] pci 0000:00:00.0: [16c3:abcd] type 01 class 0x060400
> [    0.564886] pci 0000:00:00.0: BAR 0 [mem 0x00000000-0x000fffff]
> [    0.564905] pci 0000:00:00.0: ROM [mem 0x00000000-0x0000ffff pref]
> [    0.564917] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
> [    0.564931] pci 0000:00:00.0:   bridge window [io  0x0000-0x0fff]
> [    0.564943] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
> [    0.564957] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff
> pref]
> [    0.565405] pci 0000:00:00.0: Limiting cfg_size to 512
> [    0.565455] pci 0000:00:00.0: supports D1
> [    0.565465] pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
> [    0.574310] pci 0000:01:00.0: [1b21:0612] type 00 class 0x010601
> [    0.574458] pci 0000:01:00.0: BAR 0 [io  0x0000-0x0007]
> [    0.574541] pci 0000:01:00.0: BAR 1 [io  0x0000-0x0003]
> [    0.574616] pci 0000:01:00.0: BAR 2 [io  0x0000-0x0007]
> [    0.574774] pci 0000:01:00.0: BAR 3 [io  0x0000-0x0003]
> [    0.574854] pci 0000:01:00.0: BAR 4 [io  0x0000-0x001f]
> [    0.574925] pci 0000:01:00.0: BAR 5 [mem 0x00000000-0x000001ff]
> [    0.575001] pci 0000:01:00.0: ROM [mem 0x00000000-0x0000ffff pref]
> [    0.575765] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by
> 2.5 GT/s PCIe x1 link at 0000:00:00.0 (capable of 4.000 Gb/s with 5.0 GT/s PCIe
> x1 link)
> [    0.576808] pci 0000:00:00.0: BAR 0 [mem 0x01000000-0x010fffff]: assigned
> [    0.576860] pci 0000:00:00.0: bridge window [mem 0x01100000-0x011fffff]:
> assigned
> [    0.576895] pci 0000:00:00.0: bridge window [mem 0x01200000-0x012fffff
> pref]: assigned
> [    0.576928] pci 0000:00:00.0: ROM [mem 0x01300000-0x0130ffff pref]:
> assigned
> [    0.576958] pci 0000:00:00.0: bridge window [io  0x1000-0x1fff]: assigned
> [    0.577000] pci 0000:01:00.0: ROM [mem 0x01200000-0x0120ffff pref]:
> assigned
> [    0.577033] pci 0000:01:00.0: BAR 5 [mem 0x01100000-0x011001ff]: assigned
> [    0.577087] pci 0000:01:00.0: BAR 4 [io  0x1000-0x101f]: assigned
> [    0.577212] pci 0000:01:00.0: BAR 0 [io  0x1020-0x1027]: assigned
> [    0.577273] pci 0000:01:00.0: BAR 2 [io  0x1028-0x102f]: assigned
> [    0.577326] pci 0000:01:00.0: BAR 1 [io  0x1030-0x1033]: assigned
> [    0.577377] pci 0000:01:00.0: BAR 3 [io  0x1034-0x1037]: assigned
> [    0.577429] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
> [    0.577460] pci 0000:00:00.0:   bridge window [io  0x1000-0x1fff]
> [    0.577491] pci 0000:00:00.0:   bridge window [mem 0x01100000-0x011fffff]
> [    0.577520] pci 0000:00:00.0:   bridge window [mem 0x01200000-0x012fffff
> pref]
> [    0.579109] pcieport 0000:00:00.0: PME: Signaling with IRQ 291
> [    0.580323] pcieport 0000:00:00.0: AER: enabled with IRQ 291
Hi Leonardo & Francesco:
I looked through the code changes in commit 610fa91d9863 ("PCI: imx6: Assert PERST# before enabling regulators").

I noticed there are changes to the sequence between clk_enable() and
assert_core_reset():

+       ret = imx_pcie_clk_enable(imx_pcie);
+       if (ret) {
+               dev_err(dev, "unable to enable pcie clocks: %d\n", ret);
+               goto err_reg_disable;
+       }
+
        if (pp->bridge && imx_check_flag(imx_pcie, IMX_PCIE_FLAG_HAS_LUT)) {
                pp->bridge->enable_device = imx_pcie_enable_device;
                pp->bridge->disable_device = imx_pcie_disable_device;
        }

        imx_pcie_assert_core_reset(imx_pcie);
-       imx_pcie_assert_perst(imx_pcie, true);

        if (imx_pcie->drvdata->init_phy)
                imx_pcie->drvdata->init_phy(imx_pcie);

        imx_pcie_configure_type(imx_pcie);

-       ret = imx_pcie_clk_enable(imx_pcie);
-       if (ret) {
-               dev_err(dev, "unable to enable pcie clocks: %d\n", ret);
-               goto err_reg_disable;
-       }
-

Based on v7.2-rc7, can you help to verify the new sequence below can resolve your problem or not?

diff --git a/drivers/pci/controller/dwc/pci-imx6.c b/drivers/pci/controller/dwc/pci-imx6.c
index f7389b5437dfe..f799e4b62815a 100644
--- a/drivers/pci/controller/dwc/pci-imx6.c
+++ b/drivers/pci/controller/dwc/pci-imx6.c
@@ -1388,12 +1388,6 @@ static int imx_pcie_host_init(struct dw_pcie_rp *pp)
                goto err_pwrctrl_destroy;
        }

-       ret = imx_pcie_clk_enable(imx_pcie);
-       if (ret) {
-               dev_err(dev, "unable to enable pcie clocks: %d\n", ret);
-               goto err_pwrctrl_power_off;
-       }
-
        if (pp->bridge && imx_check_flag(imx_pcie, IMX_PCIE_FLAG_HAS_LUT)) {
                pp->bridge->enable_device = imx_pcie_enable_device;
                pp->bridge->disable_device = imx_pcie_disable_device; @@ -1409,6 +1403,12 @@ static int imx_pcie_host_init(struct dw_pcie_rp *pp)

        imx_pcie_configure_type(imx_pcie);

+       ret = imx_pcie_clk_enable(imx_pcie);
+       if (ret) {
+               dev_err(dev, "unable to enable pcie clocks: %d\n", ret);
+               goto err_pwrctrl_power_off;
+       }
+
        if (imx_pcie->phy) {
                ret = phy_init(imx_pcie->phy);
                if (ret) {

Best Regards
Richard Zhu

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Francesco Dolcini]

On Wed, Aug 12, 2026 at 06:22:57AM +0000, Hongxing Zhu wrote:
> 
> NXP Confidential
> > -----Original Message-----
> > From: Francesco Dolcini <francesco@dolcini.it>
> > Sent: Tuesday, August 11, 2026 2:38 PM
> > To: Hongxing Zhu (OSS) <hongxing.zhu@oss.nxp.com>
> > Cc: Leonardo Costa <leoreis.costa@gmail.com>; Bjorn Helgaas
> > <helgaas@kernel.org>; robh@kernel.org; krzk+dt@kernel.org;
> > conor+dt@kernel.org; Frank Li <frank.li@nxp.com>; s.hauer@pengutronix.de;
> > kernel@pengutronix.de; festevam@gmail.com; leonardo.costa@toradex.com;
> > devicetree@vger.kernel.org; imx@lists.linux.dev; linux-arm-
> > kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> > regressions@lists.linux.dev; Sherry Sun <sherry.sun@nxp.com>; Manivannan
> > Sadhasivam <mani@kernel.org>; Hongxing Zhu <hongxing.zhu@nxp.com>;
> > linux-pci@vger.kernel.org
> > Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots
> >
> > On Tue, Aug 11, 2026 at 12:47:18AM +0000, Hongxing Zhu (OSS) wrote:
> > > > -----Original Message-----
> > > > From: Leonardo Costa <leoreis.costa@gmail.com>
> > > > Sent: Tuesday, August 11, 2026 2:26 AM
> > > > To: Hongxing Zhu (OSS) <hongxing.zhu@oss.nxp.com>
> > > > Cc: Bjorn Helgaas <helgaas@kernel.org>; robh@kernel.org;
> > > > krzk+dt@kernel.org; conor+dt@kernel.org; Frank Li
> > > > krzk+<frank.li@nxp.com>;
> > > > s.hauer@pengutronix.de; kernel@pengutronix.de; festevam@gmail.com;
> > > > leonardo.costa@toradex.com; devicetree@vger.kernel.org;
> > > > imx@lists.linux.dev; linux-arm-kernel@lists.infradead.org; linux-
> > > > kernel@vger.kernel.org; regressions@lists.linux.dev; Sherry Sun
> > > > <sherry.sun@nxp.com>; Manivannan Sadhasivam <mani@kernel.org>;
> > > > Hongxing Zhu <hongxing.zhu@nxp.com>; linux-pci@vger.kernel.org
> > > > Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer
> > > > boots
> > > >
> > > > On Thu, Jul 16, 2026 at 02:09:19PM -0300, Leonardo Costa wrote:
> > > > > On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
> > > > > > Hi Leonardo,
> > > > > >
> > > > > > Would you be able to test this patch on your affected boards?
> > > > > > Your testing would help expedite the merge process and ensure
> > > > > > the fix resolves the boot issue you're experiencing.
> > > > > >
> > > > > > Best Regards
> > > > > > Richard Zhu
> > > > >
> > > > > Hi Richard,
> > > > >
> > > > > Sorry for taking long to respond, I was caught up with something.
> > > > > I tested the patch and it solved the issue. I sent a Tested-by tag there.
> > > > > Thanks for looking into this!
> > > > >
> > > > > Best Regards
> > > > > Leonardo
> > > >
> > > > Hi Richard,
> > > >
> > > > That patch might have introduced/exposed a second regression where
> > > > PCI devices are not linked properly during the initialization. Sorry
> > > > for not catching this before, as I didn't have any device connected during
> > the previous test.
> > > Hi Leonardo:
> > > Sorry to hear about that.
> > > I did test commit 7678e81498e2 with one Intel NIC (82574L) connected,
> > > and I've double-checked today based on v7.2-rc7. The PCIe link can be
> > > set up properly on the i.MX6Q Sabresd board in my testing.
> > >
> > > Here are the logs:
> > > root@imx6qpdlsolox:~# lspci
> > > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > > 01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
> > > Connection root@imx6qpdlsolox:~# uname -a Linux imx6qpdlsolox
> > > 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
> > > root@imx6qpdlsolox:~# dmesg | grep pci
> > > [    0.256138] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> > > [    0.256307] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff ->
> > 0x0000000000
> > > [    0.256339] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -
> > > 0x0001000000
> > > [    0.256434] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu
> > 0x01f00000
> > > [    0.458388] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K,
> > limit 4G
> > > [    0.458492] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
> > > [    0.555294] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
> > > [    0.555783] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
> > > ...
> > >
> > > The following endpoint devices also yielded the same results.
> > > root@imx6qpdlsolox:~# lspci
> > > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > > 01:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network
> > > Adapter (PCI-Express) (rev 01) root@imx6qpdlsolox:~# uname -a Linux
> > > imx6qpdlsolox 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l
> > > GNU/Linux ...
> > >
> > > root@imx6qpdlsolox:~# lspci
> > > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > > 01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host
> > > Controller (rev 04) root@imx6qpdlsolox:~# uname -a Linux imx6qpdlsolox
> > > 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
> > >
> > > Could you provide more details of your hardware setup (board,
> > > connected devices, PERST# present or not)?
> > > This may help us identify if there's a specific scenario that triggers
> > > the regression you're experiencing.
> >
> > It's an apalis imx6, as reported already in this email thread.
> > The DT is in Linux, you can check
> > arch/arm/boot/dts/nxp/imx/imx6q-apalis-ixora-v1.2.dts every details about
> > PERST# and more.
> >
> > This is the device connected:
> >
> > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > 01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial
> > ATA Controller (rev 02)
> >
> > 01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial
> > ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
> >       Subsystem: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA
> > Controller
> >       Flags: bus master, fast devsel, latency 0, IRQ 308
> >       I/O ports at 1020 [size=8]
> >       I/O ports at 1030 [size=4]
> >       I/O ports at 1028 [size=8]
> >       I/O ports at 1034 [size=4]
> >       I/O ports at 1000 [size=32]
> >       Memory at 01100000 (32-bit, non-prefetchable) [size=512]
> >       Expansion ROM at 01200000 [virtual] [disabled] [size=64K]
> >       Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-
> >       Capabilities: [78] Power Management version 3
> >       Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0
> >       Capabilities: [100] Virtual Channel
> >       Kernel driver in use: ahci
> >       Kernel modules: ahci
> >

I just did one additional test, trying to help out Leonardo.

Unfortunately I do not have the same PCIe card available, so I tested with a

01:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [Wilkins Peak 2]
	Flags: fast devsel
	Memory at 01100000 (64-bit, non-prefetchable) [disabled] [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [40] Express Endpoint, IntMsgNum 0
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number ac-7b-a1-ff-ff-4e-a1-d8
	Capabilities: [14c] Latency Tolerance Reporting
	Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?>

no wi-fi driver is loaded (but this seems unrelevant for the issue here), but
the card is detected with the current mainline Linux 7.2.0-rc7+. I tested the
apalis SoM on both the eval carrier board and on ixora v1.2.

Same kernel config as the one failing.

So, unless I did some mistake in my manual test, the issue is related to the specific
PCIe card or some other subtle difference I cannot see yet.

For the record, the failure was detected by our CI/CD, and it is systematically
reproduced on multiple hardware boards.

Leonardo: any chance you can test with the same PCIe board that is failing?

Francesco

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Franz Schnyder]

On Wed, Aug 12, 2026 at 08:54:13AM +0200, Francesco Dolcini wrote:
> On Wed, Aug 12, 2026 at 06:22:57AM +0000, Hongxing Zhu wrote:
> > 
> > NXP Confidential
> > > -----Original Message-----
> > > From: Francesco Dolcini <francesco@dolcini.it>
> > > Sent: Tuesday, August 11, 2026 2:38 PM
> > > To: Hongxing Zhu (OSS) <hongxing.zhu@oss.nxp.com>
> > > Cc: Leonardo Costa <leoreis.costa@gmail.com>; Bjorn Helgaas
> > > <helgaas@kernel.org>; robh@kernel.org; krzk+dt@kernel.org;
> > > conor+dt@kernel.org; Frank Li <frank.li@nxp.com>; s.hauer@pengutronix.de;
> > > kernel@pengutronix.de; festevam@gmail.com; leonardo.costa@toradex.com;
> > > devicetree@vger.kernel.org; imx@lists.linux.dev; linux-arm-
> > > kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> > > regressions@lists.linux.dev; Sherry Sun <sherry.sun@nxp.com>; Manivannan
> > > Sadhasivam <mani@kernel.org>; Hongxing Zhu <hongxing.zhu@nxp.com>;
> > > linux-pci@vger.kernel.org
> > > Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots
> > >
> > > On Tue, Aug 11, 2026 at 12:47:18AM +0000, Hongxing Zhu (OSS) wrote:
> > > > > -----Original Message-----
> > > > > From: Leonardo Costa <leoreis.costa@gmail.com>
> > > > > Sent: Tuesday, August 11, 2026 2:26 AM
> > > > > To: Hongxing Zhu (OSS) <hongxing.zhu@oss.nxp.com>
> > > > > Cc: Bjorn Helgaas <helgaas@kernel.org>; robh@kernel.org;
> > > > > krzk+dt@kernel.org; conor+dt@kernel.org; Frank Li
> > > > > krzk+<frank.li@nxp.com>;
> > > > > s.hauer@pengutronix.de; kernel@pengutronix.de; festevam@gmail.com;
> > > > > leonardo.costa@toradex.com; devicetree@vger.kernel.org;
> > > > > imx@lists.linux.dev; linux-arm-kernel@lists.infradead.org; linux-
> > > > > kernel@vger.kernel.org; regressions@lists.linux.dev; Sherry Sun
> > > > > <sherry.sun@nxp.com>; Manivannan Sadhasivam <mani@kernel.org>;
> > > > > Hongxing Zhu <hongxing.zhu@nxp.com>; linux-pci@vger.kernel.org
> > > > > Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer
> > > > > boots
> > > > >
> > > > > On Thu, Jul 16, 2026 at 02:09:19PM -0300, Leonardo Costa wrote:
> > > > > > On Thu, Jul 16, 2026 at 02:15:42AM +0000, Hongxing Zhu (OSS) wrote:
> > > > > > > Hi Leonardo,
> > > > > > >
> > > > > > > Would you be able to test this patch on your affected boards?
> > > > > > > Your testing would help expedite the merge process and ensure
> > > > > > > the fix resolves the boot issue you're experiencing.
> > > > > > >
> > > > > > > Best Regards
> > > > > > > Richard Zhu
> > > > > >
> > > > > > Hi Richard,
> > > > > >
> > > > > > Sorry for taking long to respond, I was caught up with something.
> > > > > > I tested the patch and it solved the issue. I sent a Tested-by tag there.
> > > > > > Thanks for looking into this!
> > > > > >
> > > > > > Best Regards
> > > > > > Leonardo
> > > > >
> > > > > Hi Richard,
> > > > >
> > > > > That patch might have introduced/exposed a second regression where
> > > > > PCI devices are not linked properly during the initialization. Sorry
> > > > > for not catching this before, as I didn't have any device connected during
> > > the previous test.
> > > > Hi Leonardo:
> > > > Sorry to hear about that.
> > > > I did test commit 7678e81498e2 with one Intel NIC (82574L) connected,
> > > > and I've double-checked today based on v7.2-rc7. The PCIe link can be
> > > > set up properly on the i.MX6Q Sabresd board in my testing.
> > > >
> > > > Here are the logs:
> > > > root@imx6qpdlsolox:~# lspci
> > > > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > > > 01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
> > > > Connection root@imx6qpdlsolox:~# uname -a Linux imx6qpdlsolox
> > > > 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
> > > > root@imx6qpdlsolox:~# dmesg | grep pci
> > > > [    0.256138] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> > > > [    0.256307] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff ->
> > > 0x0000000000
> > > > [    0.256339] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -
> > > > 0x0001000000
> > > > [    0.256434] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu
> > > 0x01f00000
> > > > [    0.458388] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K,
> > > limit 4G
> > > > [    0.458492] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
> > > > [    0.555294] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
> > > > [    0.555783] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
> > > > ...
> > > >
> > > > The following endpoint devices also yielded the same results.
> > > > root@imx6qpdlsolox:~# lspci
> > > > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > > > 01:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network
> > > > Adapter (PCI-Express) (rev 01) root@imx6qpdlsolox:~# uname -a Linux
> > > > imx6qpdlsolox 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l
> > > > GNU/Linux ...
> > > >
> > > > root@imx6qpdlsolox:~# lspci
> > > > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > > > 01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host
> > > > Controller (rev 04) root@imx6qpdlsolox:~# uname -a Linux imx6qpdlsolox
> > > > 7.2.0-rc7 #30 SMP Tue Aug 11 00:21:26 UTC 2026 armv7l GNU/Linux
> > > >
> > > > Could you provide more details of your hardware setup (board,
> > > > connected devices, PERST# present or not)?
> > > > This may help us identify if there's a specific scenario that triggers
> > > > the regression you're experiencing.
> > >
> > > It's an apalis imx6, as reported already in this email thread.
> > > The DT is in Linux, you can check
> > > arch/arm/boot/dts/nxp/imx/imx6q-apalis-ixora-v1.2.dts every details about
> > > PERST# and more.
> > >
> > > This is the device connected:
> > >
> > > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > > 01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial
> > > ATA Controller (rev 02)
> > >
> > > 01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial
> > > ATA Controller (rev 02) (prog-if 01 [AHCI 1.0])
> > >       Subsystem: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA
> > > Controller
> > >       Flags: bus master, fast devsel, latency 0, IRQ 308
> > >       I/O ports at 1020 [size=8]
> > >       I/O ports at 1030 [size=4]
> > >       I/O ports at 1028 [size=8]
> > >       I/O ports at 1034 [size=4]
> > >       I/O ports at 1000 [size=32]
> > >       Memory at 01100000 (32-bit, non-prefetchable) [size=512]
> > >       Expansion ROM at 01200000 [virtual] [disabled] [size=64K]
> > >       Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-
> > >       Capabilities: [78] Power Management version 3
> > >       Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0
> > >       Capabilities: [100] Virtual Channel
> > >       Kernel driver in use: ahci
> > >       Kernel modules: ahci
> > >
> 
> I just did one additional test, trying to help out Leonardo.
> 
> Unfortunately I do not have the same PCIe card available, so I tested with a
> 
> 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
> 	Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [Wilkins Peak 2]
> 	Flags: fast devsel
> 	Memory at 01100000 (64-bit, non-prefetchable) [disabled] [size=8K]
> 	Capabilities: [c8] Power Management version 3
> 	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
> 	Capabilities: [40] Express Endpoint, IntMsgNum 0
> 	Capabilities: [100] Advanced Error Reporting
> 	Capabilities: [140] Device Serial Number ac-7b-a1-ff-ff-4e-a1-d8
> 	Capabilities: [14c] Latency Tolerance Reporting
> 	Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?>
> 
> no wi-fi driver is loaded (but this seems unrelevant for the issue here), but
> the card is detected with the current mainline Linux 7.2.0-rc7+. I tested the
> apalis SoM on both the eval carrier board and on ixora v1.2.
> 
> Same kernel config as the one failing.
> 
> So, unless I did some mistake in my manual test, the issue is related to the specific
> PCIe card or some other subtle difference I cannot see yet.
> 
> For the record, the failure was detected by our CI/CD, and it is systematically
> reproduced on multiple hardware boards.
> 
> Leonardo: any chance you can test with the same PCIe board that is failing?

Hi all,

I reproduced the issue on my setup (eval board + same PCIe card as in our CI/CD).

root@apalis-imx6-11486042:~# lspci
root@apalis-imx6-11486042:~# dmesg | grep pcie
[    0.162860] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
[    0.162974] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff -> 0x0000000000
[    0.163043] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -> 0x0001000000
[    0.163193] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu 0x01f00000
[    0.505056] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K, limit 4G
[    0.505230] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
[    1.508173] imx6q-pcie 1ffc000.pcie: Link failed to come up. LTSSM: POLL_CONFIG
[    1.508314] imx6q-pcie 1ffc000.pcie: probe with driver imx6q-pcie failed with error -110

After applying the new sequence proposed by Zhu, the PCIe card comes up.

root@apalis-imx6-11486042:~# lspci
00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02)
root@apalis-imx6-11486042:~# dmesg | grep pcie
[    0.162515] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
[    0.162636] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff -> 0x0000000000
[    0.162702] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -> 0x0001000000
[    0.162828] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu 0x01f00000
[    0.488893] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K, limit 4G
[    0.489033] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
[    0.591333] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
[    0.591967] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
[    0.602947] pcieport 0000:00:00.0: PME: Signaling with IRQ 291
[    0.603534] pcieport 0000:00:00.0: AER: enabled with IRQ 291

I'm completely out of the loop on this whole issue and I only helped out
to test the patch. However, I wanted to add that before applying Zhu's 
proposed sequence, I could only reproduce the issue by power cycling the
module, as rebooting alone did not trigger the issue.

kind regards

Franz

Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Francesco Dolcini]

On Thu, Aug 13, 2026 at 09:34:01AM +0200, Franz Schnyder wrote:
> On Wed, Aug 12, 2026 at 08:54:13AM +0200, Francesco Dolcini wrote:
> > So, unless I did some mistake in my manual test, the issue is related to the specific
> > PCIe card or some other subtle difference I cannot see yet.
> > 
> > For the record, the failure was detected by our CI/CD, and it is systematically
> > reproduced on multiple hardware boards.
> > 
> > Leonardo: any chance you can test with the same PCIe board that is failing?
> 
> I reproduced the issue on my setup (eval board + same PCIe card as in our CI/CD).
> 
> root@apalis-imx6-11486042:~# lspci
> root@apalis-imx6-11486042:~# dmesg | grep pcie
> [    0.162860] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> [    0.162974] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff -> 0x0000000000
> [    0.163043] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -> 0x0001000000
> [    0.163193] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu 0x01f00000
> [    0.505056] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K, limit 4G
> [    0.505230] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
> [    1.508173] imx6q-pcie 1ffc000.pcie: Link failed to come up. LTSSM: POLL_CONFIG
> [    1.508314] imx6q-pcie 1ffc000.pcie: probe with driver imx6q-pcie failed with error -110
> 
> After applying the new sequence proposed by Zhu, the PCIe card comes up.
> 
> root@apalis-imx6-11486042:~# lspci
> 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> 01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02)
> root@apalis-imx6-11486042:~# dmesg | grep pcie
> [    0.162515] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> [    0.162636] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff -> 0x0000000000
> [    0.162702] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -> 0x0001000000
> [    0.162828] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu 0x01f00000
> [    0.488893] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K, limit 4G
> [    0.489033] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
> [    0.591333] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
> [    0.591967] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
> [    0.602947] pcieport 0000:00:00.0: PME: Signaling with IRQ 291
> [    0.603534] pcieport 0000:00:00.0: AER: enabled with IRQ 291
> 
> I'm completely out of the loop on this whole issue and I only helped out
> to test the patch. However, I wanted to add that before applying Zhu's 
> proposed sequence, I could only reproduce the issue by power cycling the
> module, as rebooting alone did not trigger the issue.

Interesting. This might explain why I couldn’t reproduce the issue in my
setup, rather than the difference being caused by the specific PCIe
card.

Franz: thanks for the test.

Richard: will you submit a formal patch, so we try to finally fix this
issue?  I guess it's now too late for 7.2, so be sure to cc:stable and
have a fixes tag.

Francesco

RE: [REGRESSION] mainline/master: Apalis iMX6 no longer boots

[Hongxing Zhu (OSS)]

NXP Confidential
> -----Original Message-----
> From: Francesco Dolcini <francesco@dolcini.it>
> Sent: Thursday, August 13, 2026 3:47 PM
> To: Franz Schnyder <fra.schnyder@gmail.com>; Hongxing Zhu
> <hongxing.zhu@nxp.com>
> Cc: Francesco Dolcini <francesco@dolcini.it>; Hongxing Zhu (OSS)
> <hongxing.zhu@oss.nxp.com>; Leonardo Costa <leoreis.costa@gmail.com>;
> Bjorn Helgaas <helgaas@kernel.org>; robh@kernel.org; krzk+dt@kernel.org;
> conor+dt@kernel.org; Frank Li <frank.li@nxp.com>; s.hauer@pengutronix.de;
> kernel@pengutronix.de; festevam@gmail.com; leonardo.costa@toradex.com;
> devicetree@vger.kernel.org; imx@lists.linux.dev; linux-arm-
> kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> regressions@lists.linux.dev; Sherry Sun <sherry.sun@nxp.com>; Manivannan
> Sadhasivam <mani@kernel.org>; linux-pci@vger.kernel.org
> Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots
>
> On Thu, Aug 13, 2026 at 09:34:01AM +0200, Franz Schnyder wrote:
> > On Wed, Aug 12, 2026 at 08:54:13AM +0200, Francesco Dolcini wrote:
> > > So, unless I did some mistake in my manual test, the issue is
> > > related to the specific PCIe card or some other subtle difference I cannot see
> yet.
> > >
> > > For the record, the failure was detected by our CI/CD, and it is
> > > systematically reproduced on multiple hardware boards.
> > >
> > > Leonardo: any chance you can test with the same PCIe board that is failing?
> >
> > I reproduced the issue on my setup (eval board + same PCIe card as in our
> CI/CD).
> >
> > root@apalis-imx6-11486042:~# lspci
> > root@apalis-imx6-11486042:~# dmesg | grep pcie
> > [    0.162860] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> > [    0.162974] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff ->
> 0x0000000000
> > [    0.163043] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -
> > 0x0001000000
> > [    0.163193] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu
> 0x01f00000
> > [    0.505056] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K,
> limit 4G
> > [    0.505230] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
> > [    1.508173] imx6q-pcie 1ffc000.pcie: Link failed to come up. LTSSM:
> POLL_CONFIG
> > [    1.508314] imx6q-pcie 1ffc000.pcie: probe with driver imx6q-pcie failed
> with error -110
> >
> > After applying the new sequence proposed by Zhu, the PCIe card comes up.
> >
> > root@apalis-imx6-11486042:~# lspci
> > 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
> > 01:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062
> > Serial ATA Controller (rev 02) root@apalis-imx6-11486042:~# dmesg | grep
> pcie
> > [    0.162515] imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> > [    0.162636] imx6q-pcie 1ffc000.pcie:       IO 0x0001f80000..0x0001f8ffff ->
> 0x0000000000
> > [    0.162702] imx6q-pcie 1ffc000.pcie:      MEM 0x0001000000..0x0001efffff -
> > 0x0001000000
> > [    0.162828] imx6q-pcie 1ffc000.pcie: config reg[1] 0x01f00000 == cpu
> 0x01f00000
> > [    0.488893] imx6q-pcie 1ffc000.pcie: iATU: unroll F, 4 ob, 4 ib, align 64K,
> limit 4G
> > [    0.489033] imx6q-pcie 1ffc000.pcie: Link: Only Gen1 is enabled
> > [    0.591333] imx6q-pcie 1ffc000.pcie: PCIe Gen.1 x1 link up
> > [    0.591967] imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
> > [    0.602947] pcieport 0000:00:00.0: PME: Signaling with IRQ 291
> > [    0.603534] pcieport 0000:00:00.0: AER: enabled with IRQ 291
> >
> > I'm completely out of the loop on this whole issue and I only helped
> > out to test the patch. However, I wanted to add that before applying
> > Zhu's proposed sequence, I could only reproduce the issue by power
> > cycling the module, as rebooting alone did not trigger the issue.
>
> Interesting. This might explain why I couldn’t reproduce the issue in my setup,
> rather than the difference being caused by the specific PCIe card.
>
> Franz: thanks for the test.
>
> Richard: will you submit a formal patch, so we try to finally fix this issue?  I
> guess it's now too late for 7.2, so be sure to cc:stable and have a fixes tag.
Thanks for your reminder and Franz' tests.
I'm preparing the fix patch now.

Best Regards
Richard Zhu
>
> Francesco