From: Vlad Poenaru <vlad.wing@gmail.com>
To: Jinqian Yang <yangjinqian1@huawei.com>,
Thomas Gleixner <tglx@kernel.org>, Marc Zyngier <maz@kernel.org>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
Michael Chan <michael.chan@broadcom.com>,
Pavan Chebbi <pavan.chebbi@broadcom.com>,
Jakub Kicinski <kuba@kernel.org>,
Breno Leitao <leitao@debian.org>,
Andrew Preece <apreece@meta.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [PATCH] irqchip/gic-v3-its: Enable dynamic MSI-X allocation
Date: Thu, 22 Oct 2026 12:36:20 -0700 [thread overview]
Message-ID: <20261022193620.2152038-1-vlad.wing@gmail.com> (raw)
In-Reply-To: <20260715035437.700601-1-yangjinqian1@huawei.com>
Hi,
Commit 0d6a7c417983 ("irqchip/gic-v3-its: Enable dynamic MSI-X
allocation"), merged for v7.3-rc1, breaks bnxt_en on our loving Grace
machines. Reverting it fixes the problem on current mainline.
Hardware:
- NVIDIA Grace (Neoverse V2), ACPI, GICv3 + ITS
- Broadcom BCM57508 (BCM957508-N1200FJ), FW 230.0.165.3, bnxt_en
- The same platform with a Mellanox NIC (mlx5) is not affected
The trigger is a ring resize: a boot-time udev .link file with
RxBufferSize=max, i.e. "ethtool -G eth0 rx 4095 tx 4095". The close
path never gets the HWRM_RING_FREE completions, then TX times out and
the machine hangs:
[ 58.221] bnxt_en 0002:01:00.0 eth0: Resp cmpl intr err msg: 0x51
[ 58.221] bnxt_en 0002:01:00.0 eth0: hwrm_ring_free type 1 failed. rc:fffffff0 err:0
... (repeats every ~3.7s for every ring)
[ 215.539] bnxt_en 0002:01:00.0 eth0: NETDEV WATCHDOG: CPU: 69: transmit queue 18 timed out 5118 ms
[ 215.539] bnxt_en 0002:01:00.0 eth0: TX timeout detected, starting reset task!
Bisecting v7.2..v7.3-rc3 on this machine points at the irq-drivers
merge (8b5d31123f41), and within it:
good: 9023960b74ab ("irqchip: Remove redundant dev_err()/dev_err_probe()")
bad: 0d6a7c417983 ("irqchip/gic-v3-its: Enable dynamic MSI-X allocation")
On current mainline (f47d223627f8) the same machine fails at ~55s;
with the commit reverted it runs cleanly.
So far it only reproduces with our debug config (KASAN, lockdep,
DEBUG_PAGEALLOC, DMA_API_DEBUG, CPUMASK_OFFSTACK, ...), not with our
production config. I haven't narrowed down which option matters.
My guess is that with pci_msix_can_alloc_dyn() now true behind the ITS,
bnxt switches to dynamic MSI-X allocation and something on that path
loses the completion interrupts, but I haven't root-caused it.
Happy to test patches or collect more data.
Reported-by: Andrew Preece <apreece@meta.com>
#regzbot introduced: 0d6a7c417983b
Thanks,
Vlad
prev parent reply other threads:[~2026-10-22 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 3:54 [PATCH v3] irqchip/gic-v3-its: enable " Jinqian Yang
2026-07-15 7:15 ` [tip: irq/drivers] irqchip/gic-v3-its: Enable " tip-bot2 for Jinqian Yang
2026-10-22 19:36 ` Vlad Poenaru [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=20261022193620.2152038-1-vlad.wing@gmail.com \
--to=vlad.wing@gmail.com \
--cc=apreece@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pavan.chebbi@broadcom.com \
--cc=regressions@lists.linux.dev \
--cc=tglx@kernel.org \
--cc=yangjinqian1@huawei.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
all inboxes | Powered by JetHome®