Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Greenwalt, Paul" <paul.greenwalt@intel.com>
To: Jesse Brandeburg <jbrandeburg@cloudflare.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	 Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	"Keller, Jacob E" <jacob.e.keller@intel.com>
Subject: Re: [Intel-wired-lan] BUG: ice: E830 fails RSS table adjustment with ethtool -X
Date: Wed, 17 Dec 2025 15:14:46 -0800	[thread overview]
Message-ID: <3d40d617-a31b-4a7a-86af-66d2c938c114@intel.com> (raw)
In-Reply-To: <dddf6b9b-74f0-42cc-bf1d-5fc8b8d4df8b@cloudflare.com>



On 12/5/2025 11:37 AM, Jesse Brandeburg wrote:
> Filed at:
> https://bugzilla.kernel.org/show_bug.cgi?id=220839
> 
> Kernel: stable-6.12.58
> NIC: E830 100G dual port
> 
> When trying to adjust RSS table # of queues on E830 with
> 
> ethtool -X eth0 equal 8
> 
> we see this error in logs
> 
>    [ 6112.110022] [ T303140] ice 0000:c1:00.1: Failed to configure RSS
> hash for VSI 8, error -5
>     [ 6112.528002] [ T303170] ice 0000:c1:00.0: Failed to configure RSS
> hash for VSI 6, error -5
> 
> This command works fine on E810 nics with the same driver.
>

Hi Jesse,

I have reproduced the issue and I'm looking into.

Thanks,
Paul

> Firmware/package, and NVM version info attached to bugzilla.
> 
> We're already trying this on 6.18 but data not available yet, however
> it's still a bug.
> 


  reply	other threads:[~2025-12-17 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 19:37 [Intel-wired-lan] BUG: ice: E830 fails RSS table adjustment with ethtool -X Jesse Brandeburg
2025-12-17 23:14 ` Greenwalt, Paul [this message]
2025-12-17 23:32   ` Jesse Brandeburg via Intel-wired-lan
2026-01-12 22:18     ` Greenwalt, Paul

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=3d40d617-a31b-4a7a-86af-66d2c938c114@intel.com \
    --to=paul.greenwalt@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jbrandeburg@cloudflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.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