Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Sune Brian <briansune@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Joyce Ooi <joyce.ooi@intel.com>,
	 linux-pci@vger.kernel.org, ley.foon.tan@intel.com,
	mathias.nyman@intel.com
Subject: Re: [BUG] PCIe Stall on USB_PCI=y with SoCFPGA Root Port
Date: Tue, 3 Mar 2026 15:06:51 +0200 (EET)	[thread overview]
Message-ID: <8d5cdf11-b5ba-2b10-c2ba-76d4aedb5197@linux.intel.com> (raw)
In-Reply-To: <CAN7C2SAcJp8nAhbRT9OyLeT2YsvmX=+Y4qhBZR_WQ3aDqNHywA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2215 bytes --]

On Tue, 3 Mar 2026, Sune Brian wrote:

> On Tue, Mar 3, 2026 at 7:51 AM Bjorn Helgaas <helgaas@kernel.org> wrote:
> >
> > [+to Joyce, pcie-altera.c maintainer]
> >
> > On Sat, Feb 28, 2026 at 11:05:17PM +0800, Sune Brian wrote:
> > > Dear PCI maintainers,
> > >
> > > Root Port: Cyclone V HPS Root Port PCIe
> > > Endpoint: uPD720202 Card
> > > Kernel version: 6.12.33-g3234b1ed8956-dirty
> >
> > v6.12 is fairly old; can you reproduce a problem with v6.19 or
> > v7.0-rc1?
> 
> Had tried 6.19 same situation USB_PCI=y simply repeatable hang.
> No message shown or tells what happened.

Hi,

Has it worked with some kernel at some point in the past (in which case 
git bisect might be possible to pinpoint what broke it)?

-- 
 i.

> > > Sanity confirmation of PCIe RP:
> > > Both NVMe and Realtek WIFI cards are tested
> > > and show no major issue with MSI/MSI-X enabled.
> > >
> > > Repeatable Result:
> > > When uPD720202 card is applied onto the PCIe slot.
> > > Either module or included driver could stall during kernel boot.
> > > The stall can be resolved by setting USB_PCI=n and
> > > after boot under distro lspci -vvv can disable the card info [2].
> > > All nosmi noaspm etc are tested and state the same stall.
> > >
> > > The root port info is shown in [1].
> > > Based on the above behavior we had also tried to reflash the
> > > ROM of the uPD720202 card and no difference was shown
> > > on the stall issue.
> > > The uPD720202 card is tested on another ARM 64 board and
> > > shows no stall issue.
> >
> > Do you have any details about what the actual issue is?  I guess it's
> > some kind of hang, but you don't know exactly where in the code it
> > happens?
> 
> I can't have tried so many basic dmesg and possible runtime debug methods.
> It just simply hangs or stalls.
> Maybe more guidance on how to turn on more debug messages could help.
> 
> The best I can do to know what triggered is USB_PCI=y.
> 
> Thanks,
> Brian
> 
> >
> > > With USB_PCI=n it is sure this is driver issue between
> > > pcie-altera.c & pcie-altera-msi.c
> > >
> > > Additional boot log [3] with USB_PCI=n
> > >
> > > Thanks,
> > > Brian
> > >
> 

  reply	other threads:[~2026-03-03 13:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 15:05 [BUG] PCIe Stall on USB_PCI=y with SoCFPGA Root Port Sune Brian
2026-03-02 23:51 ` Bjorn Helgaas
2026-03-03  0:53   ` Sune Brian
2026-03-03 13:06     ` Ilpo Järvinen [this message]
2026-03-03 13:34       ` Sune Brian
2026-03-03 16:03         ` Manivannan Sadhasivam
2026-03-03 17:23           ` Sune Brian

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=8d5cdf11-b5ba-2b10-c2ba-76d4aedb5197@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=briansune@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=joyce.ooi@intel.com \
    --cc=ley.foon.tan@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mathias.nyman@intel.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