All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nimrod Oren <noren@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>, Dragos Tatulea <dtatulea@nvidia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [TEST] CX7 timeouts on reconfig w/ page pool failure injection
Date: Tue, 11 Aug 2026 10:20:52 +0300	[thread overview]
Message-ID: <7caf12fd-f63b-46f0-a5bd-e9887cb25f9d@nvidia.com> (raw)
In-Reply-To: <20260804094518.53b56d24@kernel.org>

On 04/08/2026 19:45, Jakub Kicinski wrote:
> 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.
>

Seems like the bigger culprit is the earlier xdp test, which leaves MTU
at 9000:

# # Defer Exception| net.lib.py.utils.CmdExitFailure: Command failed
# # Defer Exception| CMD: ip link set dev ens25f1np1 mtu 1500 xdpdrv off
# # Defer Exception|   EXIT: -15
# # Defer Exception|
# not ok 17 xdp.test_xdp_native_adjst_head_grow_data.ipv4
# # Totals: pass:14 fail:3 xfail:0 xpass:0 skip:0 error:0
not ok 1 selftests: drivers/net: xdp.py # TIMEOUT 360 seconds

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

I'll try to reproduce this internally and investigate what happened.

Also, I noticed that the pp-alloc test isn't properly restoring the rx
ring size due to the timeout. In the subsequent retry, it's attempting
to double it again, this time from 2K to 4K:

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

https://netdev.bots.linux.dev/logs/hwksft/CX7-dbg/results/763842/test-outputs/36-pp-alloc-fail-py-retry/stdout

The high MTU and ring size along with the heavy debug kernel likely make
the pp-alloc test significantly slower. I'll also prepare a patch to fix
this pp-alloc cleanup issue.

Thanks,
Nimrod


  parent reply	other threads:[~2026-08-11  7:21 UTC|newest]

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

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=7caf12fd-f63b-46f0-a5bd-e9887cb25f9d@nvidia.com \
    --to=noren@nvidia.com \
    --cc=dtatulea@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.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 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.