From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Nam Cao <namcao@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Lukas Wunner <lukas@wunner.de>,
Bjorn Helgaas <helgaas@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux PCI Mailing List <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Krzysztof Wilczynski <kwilczynski@kernel.org>,
Armando Budianto <sprite@gnuweeb.org>,
Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
gwml@vger.gnuweeb.org
Subject: Re: [GIT PULL v2] PCI changes for v6.17
Date: Sat, 9 Aug 2025 07:52:30 +0900 [thread overview]
Message-ID: <aJZ/rum9bZqZInr+@biznet-home.integral.gnuweeb.org> (raw)
In-Reply-To: <87ectlr8l4.fsf@yellow.woof>
+ Adding tglx as he's involved in reviewing that commit.
Context: https://lore.kernel.org/linux-pci/aJXYhfc%2F6DfcqfqF@linux.gnuweeb.org/
On Fri, Aug 08, 2025 at 08:07:03PM +0200, Nam Cao wrote:
> There is no point in bisecting before that commit, because the WARN_ON()
> is added by that commit, so you wouldn't see anything before that.
I didn't notice that. Good you pointed that out earlier.
> The WARN_ONCE() tells us that some devices down the PCI tree are
> allocating MSI, but VMD supports MSI-X only.
>
> From the backtrace:
> msi_create_device_irq_domain+0x1eb/0x290
> __pci_enable_msi_range+0x106/0x300
> pci_alloc_irq_vectors_affinity+0xc5/0x110
> pcie_portdrv_probe+0x24e/0x610
>
> It seems MSI-X are allocated first, but fail for some reason. Then
> fallback to MSI, which triggers the WARN_ON().
>
> So we need to figure out why MSI-X allocation fail.
>
> I may need to ask you to insert a bunch of printk() to help me pinpoint
> the problem. But let me stare at it first..
I can do that. Send me a git diff. I'll test it and back with the dmesg
output.
--
Ammar Faizi
next prev parent reply other threads:[~2025-08-08 22:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250801142254.GA3496192@bhelgaas>
[not found] ` <175408424863.4088284.13236765550439476565.pr-tracker-bot@kernel.org>
2025-08-07 3:34 ` [GIT PULL v2] PCI changes for v6.17 Ammar Faizi
2025-08-07 3:51 ` Lukas Wunner
2025-08-07 4:44 ` Nam Cao
2025-08-07 4:54 ` Ammar Faizi
2025-08-07 5:03 ` Nam Cao
2025-08-07 5:13 ` Ammar Faizi
2025-08-08 10:59 ` Ammar Faizi
2025-08-08 11:19 ` Ammar Faizi
2025-08-08 13:34 ` Ammar Faizi
2025-08-08 18:07 ` Nam Cao
2025-08-08 22:52 ` Ammar Faizi [this message]
2025-08-09 4:34 ` Nam Cao
2025-08-09 13:28 ` Ammar Faizi
2025-08-09 14:49 ` Nam Cao
2025-08-09 15:15 ` Ammar Faizi
2025-08-09 15:32 ` Nam Cao
2025-08-09 16:03 ` Ammar Faizi
2025-08-09 16:28 ` Nam Cao
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=aJZ/rum9bZqZInr+@biznet-home.integral.gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=helgaas@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lukas@wunner.de \
--cc=mani@kernel.org \
--cc=namcao@linutronix.de \
--cc=robh@kernel.org \
--cc=sprite@gnuweeb.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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