All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Nimrod Oren <noren@nvidia.com>, Dragos Tatulea <dtatulea@nvidia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [TEST] CX7 timeouts on reconfig w/ page pool failure injection
Date: Tue, 4 Aug 2026 09:45:18 -0700	[thread overview]
Message-ID: <20260804094518.53b56d24@kernel.org> (raw)

Hi!

The CX7 testing in NIPA is looking pretty good, one major source of
noise, tho, is that the pp-alloc test sometimes locks rtnl for
a minute.

Here's a failure in that test itself:

# # Exception| subprocess.TimeoutExpired: Command '['ethtool', '-G', 'ens25f1np1', 'rx', '2048']' timed out after 20 seconds
# # Exception| 
# not ok 1 pp_alloc_fail.test_pp_alloc

https://netdev.bots.linux.dev/logview.html?f=/logs/hwksft/CX7-dbg/results/763842/test-outputs/36-pp-alloc-fail-py/stdout

Then the next test that runs also times out during setup:

# subprocess.TimeoutExpired: Command '['ip', '--json', '-d', 'link', 'show', 'dev', 'ens25f1np1']' timed out after 20 seconds
not ok 1 selftests: drivers/net/hw: rss_api.py # exit=1

https://netdev.bots.linux.dev/logs/hwksft/CX7-dbg/results/763842/test-outputs/37-rss-api-py/stdout

pp_alloc test can fail, but spilling into the next test is a problem.

At the retry things clear up enough to return to happiness, tho:

https://netdev.bots.linux.dev/logs/hwksft/CX7-dbg/results/763842/test-outputs/37-rss-api-py-retry/stdout

I haven't try to dig into where it is blocked but does this ring any
bells?

             reply	other threads:[~2026-08-04 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 16:45 Jakub Kicinski [this message]
2026-08-04 17:16 ` [TEST] CX7 timeouts on reconfig w/ page pool failure injection Dragos Tatulea
2026-08-04 19:44   ` Jakub Kicinski
2026-08-11  7:20 ` Nimrod Oren
2026-08-11 15:04   ` Jakub Kicinski
2026-08-11 16:57     ` Nimrod Oren
2026-08-11 17:38       ` Jakub Kicinski

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=20260804094518.53b56d24@kernel.org \
    --to=kuba@kernel.org \
    --cc=dtatulea@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=noren@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.