E810-XXV ice driver: Error setting promisc mode on VSI 6 (rc=-17) in linux kernel >= 5.18.y

[JaroslavPulchart]

Hello

it is not possible to set promisc mode on E810-XXV network card with latest stable linux kernel 5.18.y.  The issue is easy to reproduce by simple setting  promisc on on physical interface:

$ ip link set em1 promisc on

the kernel message report:

$ dmesg -T | tail -n 1
[Thu Jun  9 08:48:19 2022] ice 0000:31:00.0: Error setting promisc
mode on VSI 6 (rc=-17)

This issue is not observer with previous linux stable kernel line 5.17.y.

Best regards,

Jaroslav Pulchart

[Caguicla_Intel]

Hello JaroslavPulchart,

Thank you for posting in Intel Ethernet Communities. 

We are sorry to hear that you are encountering issue with your E810-XXV network card with latest stable Linux kernel 5.18.y. For us to check your query, please provide the following information.

1. Exact Operating System used

2. Driver version used

3. Exact model of your E810-XXV. Is it E810XXV-DA2 or DA4? This is just for our record purposes. 

4.NVM version used

Awaiting to your reply. 

We will follow up after 3 business days in case we don't hear from you. 

Best regards,

Crisselle C.

Intel® Customer Support

[JaroslavPulchart]

Hello,

> 1. Exact Operating System used

CentOS 8 Stream + latest stable vanilla upstream kernel (5.18.y)

> 2. Driver version used

The ice module reports same version as is the vanilla kernel (5.18.y)

    $ ethtool -i em1
    driver: ice
    version: 5.18.5...

> 3. Exact model of your E810-XXV. Is it E810XXV-DA2 or DA4? This is just for our record purposes. 

I expect it is a E810XXV-DA2 model as we are using 2-port option:

* Intel Corporation Ethernet 25G 2P E810-XXV OCP

* Intel Corporation Ethernet 25G 2P E810-XXV Adapter

> 4.NVM version used

None. Using drivers from latest stable vanilla linux kernels only.

Best,

Jaroslav P.

[Caguicla_Intel]

Hello Jaroslav,

Thank you for providing the requested information. 

Before we further check this request with our engineers, can you share if you already tried latest driver from our site? If yes, please share the result with us. 

Intel® Network Adapter Driver for E810 Series Devices under Linux*

https://www.intel.com/content/www/us/en/download/19630/intel-network-adapter-driver-for-e810-series-devices-under-linux.html

Hoping to hear from you soon. 

Should there be no reply, we will follow up after 3 business days. 

Best regards,

Crisselle C.

Intel Customer Support

[JaroslavPulchart]

Hello,

yes, I try to compile 1.8.9 as a kmod for 5.18.y. Unfortunately it is not compatible.

There are two visible issues:

/1/ incompatible pointers types in ice_set_ringparam and ice_get_ringparam functions (ice-1.8.9/src/ice_ethtool.c). This is easy to fix by this patch:

--- ice-1.8.9/src/ice_ethtool.c 2022-06-19 10:26:42.504466438 +0200
+++ ice-1.8.9/src/ice_ethtool.c 2022-06-19 10:29:42.052198912 +0200
@@ -4511,7 +4511,9 @@
}

static void
-ice_get_ringparam(struct net_device *netdev, struct ethtool_ringparam *ring)
+ice_get_ringparam(struct net_device *netdev, struct ethtool_ringparam *ring,
+ struct kernel_ethtool_ringparam *kernel_ring,
+ struct netlink_ext_ack *extack)
{
struct ice_netdev_priv *np = netdev_priv(netdev);
struct ice_vsi *vsi = np->vsi;
@@ -4529,7 +4531,9 @@
}

static int
-ice_set_ringparam(struct net_device *netdev, struct ethtool_ringparam *ring)
+ice_set_ringparam(struct net_device *netdev, struct ethtool_ringparam *ring,
+ struct kernel_ethtool_ringparam *kernel_ring,
+ struct netlink_ext_ack *extack)
{
struct ice_ring *tx_rings = NULL, *rx_rings = NULL;
struct ice_netdev_priv *np = netdev_priv(netdev);

/2/ irdma integration is broken. See "depmod" output:

kernel/drivers/infiniband/hw/irdma/irdma.ko.xz needs unknown symbol ice_del_rdma_qset
kernel/drivers/infiniband/hw/irdma/irdma.ko.xz needs unknown symbol ice_add_rdma_qset
kernel/drivers/infiniband/hw/irdma/irdma.ko.xz needs unknown symbol ice_rdma_update_vsi_filter
kernel/drivers/infiniband/hw/irdma/irdma.ko.xz needs unknown symbol ice_rdma_request_reset
kernel/drivers/infiniband/hw/irdma/irdma.ko.xz needs unknown symbol ice_get_qos_params

due to them I decided to not install it on the servers as I cannot be sure if something hidden to my eyes will breaks network.

Best,

Jaroslav P.

[Caguicla_Intel]

Hello Jaroslav,

Thank you for the reply.

Please allow us to further check on this request. We will give you an update as soon as possible but no later than 3 business days. 

Hoping for your kind patience. 

Best regards,

Crisselle C.

Intel Customer Support

[Caguicla_Intel]

Hello Jaroslav,

Thank you for the patience on this matter. 

Please refer to below feedback from our engineers and feel free to let us know if you have additional questions or clarifications. 

Please report the issue on sourceforge as it only occurs on ice-1.8.9. They have a dedicated group to support and assist you. It requires a login for you to post and request an assistance.

Intel Ethernet Drivers and Utilities | Support for Intel Ethernet Drivers and Utilities at SourceForge.net

https://sourceforge.net/projects/e1000/support

Awaiting to your reply.

We will follow up after 3 business days in case we don't hear from you. 

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Jaroslav,

Good day!

This is just a follow up to check if you read our previous update. If yes, please confirm and let us know if you have additional questions or clarifications on this request. 

Hoping to hear from you soon. 

Should there be no response, we will follow up after 3 business days.

Best regards,

Crisselle C.

Intel Customer Support 

[JaroslavPulchart]

Hello,

I read it. The external ice kmod driver is not a subject of this issue report. I'm still waiting about intel's fix into 5.18.y or newer linux stable kernels. Do you have some news about it? Did engineering try to reproduce it and are working on the fix?

Best,

Jaroslav P.

[Caguicla_Intel]

Hello Jaroslav,

Thank you for the reply. 

Please allow us to forward your feedback to our engineers. We will give you an update as soon as we heard from them but no later than 3 business days. 

Best regards,

Crisselle C.

Intel Customer Support

[Caguicla_Intel]

Hello Jaroslav,

Please accept our apologies for the delay on this matter.

Our engineers are still checking on this one and we ask for your kind cooperation to give us more time with investigation. Rest assured that we will give you an update as soon as we heard from them but no later than 3 business days. 

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Jaroslav,

Thank you for the patience. 

Please be informed that our engineers acknowledged the issue and the fix will be on the next ice driver release 1.9.x. Release is scheduled for this month but it is still subject to change. 

Feel free to let us know if you have additional questions or clarifications. 

Awaiting to your reply. 

We will follow up after 3 business days in case we don't hear from you. 

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Jaroslav,

Good day!

This is just a follow up to check if you read our update. If yes, please confirm and let us know if you have questions or clarifications. 

Hoping to hear from you soon. 

Should there be no reply, we will follow up after 3 business days. 

Best regards,

Crisselle C.

Intel® Customer Support 

[JaroslavPulchart]

Hello

we received a patch set from intel engineers for ice driver for current in tree 5.18.y ice driver. We build the 5.18.y + ice driver patches and it slowed our issue. Do you know when it will be properly merged to the ice in tree kernel stable version?

This sentence makes no sense for me:

> ".. the fix will be on the next ice driver release 1.9.x. Release is scheduled for this month but it is still subject to change ..."

why do you wait several weeks for release of a bugfix? The bug makes Intel E810 a non working networking piece of HW. Why not to release a hotfix asap when fix is available?

Best,

Jaroslav P.

[Caguicla_Intel]

Hello Jaroslav,

Thank you for the reply. 

Please allow us to forward your feedback and clarifications to our engineers. We will give you an update once we heard from them but no later than 3 business days. 

Hoping for your kind patience.

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Jaroslav,

Thank you for the patience on this matter. 

Please see below feedback from our engineering team. 

We understand that this is an important fix for you. This fix however coincides with the release of CVL 4.0 NVM. This is why it is attached to Release 27.5 and is not released on a separate schedule.

Release is now trending for next week (WW30). We hope for your kind patience on this and we will let you know first thing when it is available for download.

Feel free to let us know if you have questions or clarifications. 

Best regards,

Crisselle C.

Intel® Customer Support

[Mike_Intel]

Hello Jaroslav,

Thank you for the patience on this matter. 

We just want to update you that we are still waiting for the confirmation of the release of version 27.5. We will update you immediately once we have confirmation.

Feel free to let us know if you have questions or clarifications. 

Best regards,

Michael L.

Intel® Customer Support

[Caguicla_Intel]

Hello Jaroslav,

Thank you for the patience on this matter. 

Please be informed that 27.5 is now available for download. This includes Columbiaville NVM 4.0.

This release also includes ice-1.9.11.tar.gz driver with the following OS Support:

• RHEL 9.0
• RHEL 8.6
• SLES 15 SP4
• Ubuntu 22.04

Intel® Ethernet Adapter Complete Driver Pack

https://www.intel.com/content/www/us/en/download/15084/intel-ethernet-adapter-complete-driver-pack.html

Feel free to let us know if you have questions or clarifications. 

Awaiting to your reply. 

We will follow up after 3 business days in case we don't hear from you. 

Best regards,

Crisselle C.

Intel® Customer Support

[JaroslavPulchart]

Hello,

good to know the out of the tree ice driver is fixed. However my subject report is about ice driver in upstream kernel 5.18.y.  When the fix will be promoted to upstream kernel?

Best,

Jaroslav P.

[Caguicla_Intel]

Hello Jaroslav,

Thank you for the prompt reply. 

Please allow us to check it with our engineers. We will get back to you within 3 business days. 

Hoping for your kind patience. 

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Jaroslav,

Good day!

This is just an update to inform you that we already re-escalated this request to our engineers and they are still looking into it. Rest assured that we will give you an update once we heard update from them.

Please expect another message no later than 3 business days.

Best regards,

Crisselle C.

Intel® Customer Support