Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
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" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	Frank Li <frank.li@nxp.com>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"leonardo.costa@toradex.com" <leonardo.costa@toradex.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	Sherry Sun <sherry.sun@nxp.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots
Date: Thu, 13 Aug 2026 09:46:53 +0200	[thread overview]
Message-ID: <20260813074653.GA11024@francesco-nb> (raw)
In-Reply-To: <t65y5d54axtksbfs7r4olcefqhwm6m4dz3njgnrnf7fcotj74i@o7avoznlafbj>

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



  reply	other threads:[~2026-08-13  7:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 14:34 [REGRESSION] mainline/master: Apalis iMX6 no longer boots Leonardo Costa
2026-06-29 20:18 ` Frank Li
2026-07-07  6:30   ` Hongxing Zhu (OSS)
2026-07-15 23:47 ` Bjorn Helgaas
2026-07-16  2:15   ` Hongxing Zhu (OSS)
2026-07-16 16:40     ` Bjorn Helgaas
2026-07-16 17:16       ` Thorsten Leemhuis
2026-07-16 17:28         ` Bjorn Helgaas
2026-07-16 17:09     ` Leonardo Costa
2026-08-10 18:26       ` Leonardo Costa
2026-08-11  0:47         ` Hongxing Zhu (OSS)
2026-08-11  6:37           ` Francesco Dolcini
2026-08-12  6:22             ` Hongxing Zhu
2026-08-12  6:54               ` Francesco Dolcini
2026-08-13  7:34                 ` Franz Schnyder
2026-08-13  7:46                   ` Francesco Dolcini [this message]
2026-08-13  7:49                     ` Hongxing Zhu (OSS)

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=20260813074653.GA11024@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=fra.schnyder@gmail.com \
    --cc=frank.li@nxp.com \
    --cc=helgaas@kernel.org \
    --cc=hongxing.zhu@nxp.com \
    --cc=hongxing.zhu@oss.nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=leonardo.costa@toradex.com \
    --cc=leoreis.costa@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sherry.sun@nxp.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