From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8F8CCC5CFDB for ; Thu, 13 Aug 2026 07:47:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=OasgZ2lwasgL8zJh7tgHLLPMWzK9RGYBY8M5hc2VuyU=; b=VdTZSaEnuPRszOUl8lYbB580L3 Od9phU0BWizLmJGBMxQq8eW64OGyGJzWKibeWBDdz/W5PNaw70qS39cYKp5Qdk7r9rL8YhGeGwGke oTOruGJxVwj8hmYoqENC8FrFv/B7OtMcLCDsUfjtuB1eCiln0dlMcgFTboAh9CNAovZAxUacvC+Jm P4twYQT3OFjQhS+xBB0RTrUvojLKun7fFgvFsDqCty3xtmVdVdZsC33wZL0N2QBW1plNx+CoO3793 y9Q2zWhohZmwkFNVI9bUpfl4xZv1QNvcpeP97in0h0cb/z/u1iHrm3dX4Ackpv7GXCP8nBr2Dyoas 6zbehhPA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wuQ9d-000000002KM-1csP; Thu, 13 Aug 2026 07:47:09 +0000 Received: from mail11.truemail.it ([217.194.8.81]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wuQ9Z-000000002JT-1d03 for linux-arm-kernel@lists.infradead.org; Thu, 13 Aug 2026 07:47:08 +0000 Received: from francesco-nb (2-224-16-253.ip168.fastwebnet.it [2.224.16.253]) by mail11.truemail.it (Postfix) with ESMTPA id 2B1391F952; Thu, 13 Aug 2026 09:46:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dolcini.it; s=default; t=1786607219; bh=OasgZ2lwasgL8zJh7tgHLLPMWzK9RGYBY8M5hc2VuyU=; h=From:To:Subject; b=Gru5+8zYKMLdaNoPB+Z1nflAJYTs7HqUDNQcbOosHwbUAK0KJX+Y0tNRdrmqBgxfE LiArpKa00xOVApQi9ab1f2mDYTblFoxOeoGNUf+4O9M2tYYL4wTYZblLjvPwdXFN9H D63jAoT4hg8+34KIArn7TJt0XP3NHyBHgHfBS5lacSs3QdcuouFaIjqRqokHDCutXR oTHMF0HIAeVEjS+cn7gJOzyrmmo9Pwce2MZIeMviV26KiqaIZD/S/401aDKffjHw9Y ssUhwqk9OthZ4vxhAxT1wZp7oGGaVEpuKr7Ywf/jR0Ge3UvIUHyupzKNIWSIjQ1b1D xkqWViq6xoH5w== Date: Thu, 13 Aug 2026 09:46:53 +0200 From: Francesco Dolcini To: Franz Schnyder , Hongxing Zhu Cc: Francesco Dolcini , "Hongxing Zhu (OSS)" , Leonardo Costa , Bjorn Helgaas , "robh@kernel.org" , "krzk+dt@kernel.org" , "conor+dt@kernel.org" , Frank Li , "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 , Manivannan Sadhasivam , "linux-pci@vger.kernel.org" Subject: Re: [REGRESSION] mainline/master: Apalis iMX6 no longer boots Message-ID: <20260813074653.GA11024@francesco-nb> References: <20260629143439.361560-1-leoreis.costa@gmail.com> <20260715234736.GA288957@bhelgaas> <3hxiy6aaiagt5zunntpidaeqc4or4wrebf7mu7asvyyibqmvo2@xhvasdqp64rw> <20260811063752.GA7332@francesco-nb> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260813_004706_648867_01A3F888 X-CRM114-Status: GOOD ( 17.26 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org 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