From: Jakub Kicinski <kuba@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Tariq Toukan <tariqt@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
network dev <netdev@vger.kernel.org>,
Matthieu Baerts <matttbe@kernel.org>
Subject: Re: nipa H/W testing suddenly failing on CX7
Date: Fri, 23 Oct 2026 08:27:35 -0700 [thread overview]
Message-ID: <20261023082735.7103e573@kernel.org> (raw)
In-Reply-To: <06502f83-f22a-4522-9a30-60b2478a8c2c@redhat.com>
On Fri, 23 Oct 2026 16:01:48 +0200 Paolo Abeni wrote:
> Hi,
>
> Mat noted that H/W self-tests suddenly started failing on the
> mentioned NIC:
>
> https://netdev.bots.linux.dev/flakes.html?min-flip=0&br-cnt=20&br-pfx=net-next-hw&ld-remote=netdev-CX7
>
> Judging from the test output, GRO stopped aggregating and the
> driver exposes a single queue?!?
>
> I could not spot anything obviously wrong in the relevant
> batch:
>
> https://netdev.bots.linux.dev/branch_deltas/net-next-hw-2026-10-22--00-00.html
>
> Could you please have a look?
FWIW I think it's the garbage check added to page pool, which Paolo
already identified. Please ignore.
Side note, I don't think we should be expecting vendors to pay
attention to netdev CI. We can set up a group of community developers
who would be willing / able to jump on such issues if maintainers
are overloaded. Vendor help is obviously welcome if voluntary
but I feel like I implied/promised in the past that the CI will not
be a burden to vendors, and this email goes against that.
prev parent reply other threads:[~2026-10-23 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 14:01 nipa H/W testing suddenly failing on CX7 Paolo Abeni
2026-10-23 15:27 ` Jakub Kicinski [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=20261023082735.7103e573@kernel.org \
--to=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=matttbe@kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.