Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Hongxing Zhu <hongxing.zhu@nxp.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
	Frank Li <frank.li@nxp.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
	"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
	"kwilczynski@kernel.org" <kwilczynski@kernel.org>,
	"mani@kernel.org" <mani@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>
Subject: Re: Non systematic PCIe error on resume on i.MX8QP on Linux 7.2
Date: Mon, 20 Jul 2026 11:38:31 +0200	[thread overview]
Message-ID: <20260720093831.GC52182@francesco-nb> (raw)
In-Reply-To: <GV2PR04MB1201926DADEFA97128E7C8CA68CC32@GV2PR04MB12019.eurprd04.prod.outlook.com>

On Mon, Jul 20, 2026 at 09:16:27AM +0000, Hongxing Zhu wrote:
> > -----Original Message-----
> > From: Francesco Dolcini <francesco@dolcini.it>
> > Sent: Monday, July 20, 2026 1:28 PM
> > To: Hongxing Zhu <hongxing.zhu@nxp.com>; Frank Li <frank.li@nxp.com>; linux-
> > pci@vger.kernel.org; imx@lists.linux.dev
> > Cc: l.stach@pengutronix.de; lpieralisi@kernel.org; kwilczynski@kernel.org;
> > mani@kernel.org; robh@kernel.org; bhelgaas@google.com;
> > s.hauer@pengutronix.de; kernel@pengutronix.de; festevam@gmail.com; linux-
> > pci@vger.kernel.org
> > Subject: Non systematic PCIe error on resume on i.MX8QP on Linux 7.2
> > 
> > Hello,
> > our CI spotted this error on resume. It is not systematic, and it is possible that this
> > is not a new issue from 7.2.
> > 
> > Does it rings any bell?
> > 
> > [  745.849237] imx8qm-hsio-phy 5f180000.phy: HSIO_PM_REQ_CORE_RST is set
> > [  745.855800] phy phy-5f180000.phy.1: phy poweron failed --> -110
> Based on the log, the PHY initialization is failing during resume.  I'll set
> up a platform on my end to see if I can reproduce this issue consistently.

Thanks for the support, appreciated.

> BTW, is this occurring on the i.MX8QM MEK board?
The issue is on apalis-imx8 (you can find the DT in the usual place in
the linux kernel tree).

> What's the frequency of occurrence in CI (failure rate)?
The last batch was 3 failure in 10 executions, so 30%.

Francesco



      reply	other threads:[~2026-07-20  9:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  5:27 Non systematic PCIe error on resume on i.MX8QP on Linux 7.2 Francesco Dolcini
2026-07-20  9:16 ` Hongxing Zhu
2026-07-20  9:38   ` Francesco Dolcini [this message]

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=20260720093831.GC52182@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=bhelgaas@google.com \
    --cc=festevam@gmail.com \
    --cc=frank.li@nxp.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=kwilczynski@kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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