[ice] `rx_errros` is too sensitive to IP/TCP attack packets (Intel E810-XXVDA4)

[Shiu202050]

When using Intel E810-XXVDA4, there is an issue where rx_errors easily increases due to attack packets.

After some investigation, I found that the E810 controller counts the checksum errors separately for each layer, with separate counters.

See
- Intel ® Ethernet Controller E810 Datasheet
    - https://www.intel.co.jp/content/www/jp/ja/content-details/613875/intel-ethernet-controller-e810-datasheet.html

         - 7.6.3.1 Status/Error.0 Field
         - 7.6.3.2 Status/Error.1 Field

On the other hand, the 'ice' driver aggregated the checksum errors from all network layers into 'hw_csum_rx_error'.

See
- https://github.com/torvalds/linux/blob/v6.13/drivers/net/ethernet/intel/ice/ice_txrx_lib.c#L122-L150

At last, 'hw_csum_rx_error' is added to 'rx_errors'.

See
- https://github.com/torvalds/linux/blob/v6.13/drivers/net/ethernet/intel/ice/ice_main.c#L6976-L6990

Normally, a broken NIC can be identified by an increment in the 'rx_length_errors' value.

However, it can be a problem if there is a slight contact failure (such as compatibility issues between GIGABYTE servers and Intel genuine NICs).

In this case, only the checksum error counter will increase, making it impossible to distinguish between a poor connection and an attack packet.

This causes problems in hardware monitoring operations.

Is it possible to separate the IP/TCP bad checksum counters from 'rx_errors' in the 'ice' driver implementation?

[Simon-Intel]

Hi Shiu202050,

Thank you for reaching out to the Intel support. We acknowledge receipt of your concern and want to assure you that assisting you is our top priority. To effectively troubleshoot the issue you're facing, we require some additional information from your end.

Could you kindly provide the following details?

1. System/board details:

2. Please share front and back pictures of the network card with the serial number clearly visible.

Your prompt response with this information will greatly assist us in diagnosing and resolving the issue as quickly as possible.

We look forward to hearing from you soon.

Best Regards,

Simon

Intel Customer Support Technician

[Simon-Intel]

Hi Shiu202050,

Good Day!

This is the first follow-up regarding the issue you reported to us.

I wanted to inquire whether you had the opportunity to provide the details requested in my previous message.

Feel free to reply to this message, and we'll be more than happy to assist you further.

Regards,

Simon

Intel Customer Support Technician

[Shiu202050]

Thank you for your reply.
And, sorry for my late reply.

This is a first server's detail.

However, I cannot enable to take photos. This is a running production server not easy to stop.
I cannot get the serial number from the system information.

Each network is connectd to…

- enp193s0f0: global network (active)
- enp193s0f1: local network (active)
- enp193s0f2: global network (backup)
- enp193s0f3: local network (active)

Some error counters are increased by my test command.

`nmap --badsum -sS <IP address>`

```

##
# errors (ethtool)
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ for i in enp193s0f{0..3}; do echo "-- $i --"; ethtool -S "$i" | grep -e err -e bad; echo; done
-- enp193s0f0 --
tx_errors: 0
tx_errors.nic: 0
rx_csum_bad.nic: 6600969
rx_length_errors.nic: 0
rx_crc_errors.nic: 0

-- enp193s0f1 --
tx_errors: 0
tx_errors.nic: 0
rx_csum_bad.nic: 0
rx_length_errors.nic: 0
rx_crc_errors.nic: 0

-- enp193s0f2 --
tx_errors: 0
tx_errors.nic: 0
rx_csum_bad.nic: 30615
rx_length_errors.nic: 0
rx_crc_errors.nic: 0

-- enp193s0f3 --
tx_errors: 0
tx_errors.nic: 0
rx_csum_bad.nic: 0
rx_length_errors.nic: 0
rx_crc_errors.nic: 0

##
# errors (/sys)
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ grep -v ^0$ /sys/class/net/enp193*/statistics/*err*
/sys/class/net/enp193s0f0/statistics/rx_errors:6600969
/sys/class/net/enp193s0f2/statistics/rx_errors:30615

##
# NIC infomation (ethtool)
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ ethtool -i enp193s0f0
driver: ice
version: 5.15.0-76-generic
firmware-version: 3.20 0x8000d833 1.3146.0
expansion-rom-version:
bus-info: 0000:c1:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

##
# udevinfo
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ sudo udevadm info --path /sys/class/net/enp193s0f0
P: /devices/pci0000:c0/0000:c0:01.1/0000:c1:00.0/net/enp193s0f0
L: 0
E: DEVPATH=/devices/pci0000:c0/0000:c0:01.1/0000:c1:00.0/net/enp193s0f0
E: INTERFACE=enp193s0f0
E: IFINDEX=4
E: SUBSYSTEM=net
E: USEC_INITIALIZED=10402283
E: ID_MM_CANDIDATE=1
E: ID_NET_NAMING_SCHEME=v249
E: ID_NET_NAME_PATH=enp193s0f0
E: ID_BUS=pci
E: ID_VENDOR_ID=0x8086
E: ID_MODEL_ID=0x1593
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Intel Corporation
E: ID_MODEL_FROM_DATABASE=Ethernet Controller E810-C for SFP (Ethernet Network Adapter E810-XXV-4)
E: ID_PATH=pci-0000:c1:00.0
E: ID_PATH_TAG=pci-0000_c1_00_0
E: ID_NET_DRIVER=ice
E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link
E: ID_NET_NAME=enp193s0f0
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp193s0f0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

##
# NIC information (lspci)
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ sudo lspci -s c1:00.0 -vvv
c1:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)
Subsystem: Intel Corporation Ethernet Network Adapter E810-XXV-4
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 386
Region 0: Memory at 20092000000 (64-bit, prefetchable) [size=32M]
Region 3: Memory at 2009c000000 (64-bit, prefetchable) [size=64K]
Expansion ROM at 9a500000 [disabled] [size=1M]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [70] MSI-X: Enable+ Count=512 Masked-
Vector table: BAR=3 offset=00000000
PBA: BAR=3 offset=00008000
Capabilities: [a0] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 512 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend+
LnkCap: Port #0, Speed 16GT/s, Width x16, ASPM not supported
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 16GT/s (ok), Width x16 (ok)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range AB, TimeoutDis+ NROPrPrP- LTR-
10BitTagComp+ 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix+, MaxEETLPPrefixes 1
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS- TPHComp- ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
LnkCtl2: Target Link Speed: 16GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+ EqualizationPhase1+
EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: unsupported
Capabilities: [e0] Vital Product Data
Product Name: Intel(R) Ethernet Network Adapter E810-XXVDA4
Read-only fields:
[V1] Vendor specific: Intel(R) Ethernet Network Adapter E810-XXVDA4
[PN] Part number: K92046-006
[SN] Serial number: B49691A59DAC
[V2] Vendor specific: 4420
[RV] Reserved: checksum good, 0 byte(s) reserved
End
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO+ CmpltAbrt- UnxCmplt+ RxOF+ MalfTLP+ ECRC+ UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn+ ECRCChkCap+ ECRCChkEn+
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [148 v1] Alternative Routing-ID Interpretation (ARI)
ARICap: MFVC- ACS-, Next Function: 1
ARICtl: MFVC- ACS-, Function Group: 0
Capabilities: [150 v1] Device Serial Number b4-96-91-ff-ff-a5-9d-ac
Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV)
IOVCap: Migration-, Interrupt Message Number: 000
IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy+
IOVSta: Migration-
Initial VFs: 64, Total VFs: 64, Number of VFs: 0, Function Dependency Link: 00
VF offset: 8, stride: 1, Device ID: 1889
Supported Page Size: 00000553, System Page Size: 00000001
Region 0: Memory at 000002009a000000 (64-bit, prefetchable)
Region 3: Memory at 000002009c040000 (64-bit, prefetchable)
VF Migration: offset: 00000000, BIR: 0
Capabilities: [1a0 v1] Transaction Processing Hints
Device specific mode supported
No steering table available
Capabilities: [1b0 v1] Access Control Services
ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
Capabilities: [1d0 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Capabilities: [200 v1] Data Link Feature <?>
Capabilities: [210 v1] Physical Layer 16.0 GT/s <?>
Capabilities: [250 v1] Lane Margining at the Receiver <?>
Kernel driver in use: ice
Kernel modules: ice

##
# Linux Kernel Version / Linux Distribution Version
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ uname -a
Linux vm2022-06-a 5.15.0-76-generic #83-Ubuntu SMP Thu Jun 15 19:16:32 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

k-shibata@vm2022-06-a[PRODUCTION]:~$ lsb_release -ir
Distributor ID: Ubuntu
Release: 22.04

##
# SMBIOS Infomation (rack-server)
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ sudo dmidecode -t chassis
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
Manufacturer: GIGABYTE
Type: Rack Mount Chassis
Lock: Not Present
Version: 01234567
Serial Number: 01234567890123456789AB
Asset Tag: 01234567890123456789AB
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: 01234567890123456789AB

##
# SMBIOS Infomation (Motherboards)
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ sudo dmidecode -t baseboard
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: GIGABYTE
Product Name: MZ32-AR1-00
Version: 02010201
Serial Number: LH7NE100100
Asset Tag: 01234567890123456789AB
Features:
Board is a hosting board
Board is removable
Board is replaceable
Location In Chassis: 01234567890123456789AB
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

##
# BIOS
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ sudo dmidecode -t bios
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: GIGABYTE
Version: M10
Release Date: 11/23/2021
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
5.25"/360 kB floppy services are supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.22

```

[Shiu202050]

2nd server's chassis is same as 1st server.
But,  2nd server is used "Broadcom P425G" instead of "Intel E810-XXVDA4"

See it

```

##
# errors (ethtool)
##

k-shibata@vm2022-06-b[PRODUCTION]:~$ for i in enp193s0f{0np0,1np1,2np2,3np3}; do echo "-- $i --"; ethtool -S "$i" | grep -e err -e bad; echo; done
-- enp193s0f0np0 --
[0]: rx_errors: 0
[0]: tx_errors: 0
[0]: rx_tpa_errors: 0
[0]: rx_l4_csum_errors: 30929
[0]: rx_buf_errors: 0
[1]: rx_errors: 0
[1]: tx_errors: 0
[1]: rx_tpa_errors: 0
[1]: rx_l4_csum_errors: 31670
[1]: rx_buf_errors: 0
[2]: rx_errors: 0
[2]: tx_errors: 0
[2]: rx_tpa_errors: 0
[2]: rx_l4_csum_errors: 30736
[2]: rx_buf_errors: 0
[3]: rx_errors: 0
[3]: tx_errors: 0
[3]: rx_tpa_errors: 0
[3]: rx_l4_csum_errors: 33767
[3]: rx_buf_errors: 0
[4]: rx_errors: 0
[4]: tx_errors: 0
[4]: rx_tpa_errors: 0
[4]: rx_l4_csum_errors: 34544
[4]: rx_buf_errors: 0
[5]: rx_errors: 0
[5]: tx_errors: 0
[5]: rx_tpa_errors: 0
[5]: rx_l4_csum_errors: 32491
[5]: rx_buf_errors: 0
[6]: rx_errors: 0
[6]: tx_errors: 0
[6]: rx_tpa_errors: 0
[6]: rx_l4_csum_errors: 32148
[6]: rx_buf_errors: 0
[7]: rx_errors: 0
[7]: tx_errors: 0
[7]: rx_tpa_errors: 0
[7]: rx_l4_csum_errors: 36848
[7]: rx_buf_errors: 0
rx_fcs_err_frames: 0
rx_align_err_frames: 0
rx_mtu_err_frames: 0
rx_stat_err: 0
tx_fcs_err_frames: 0
tx_err: 0
tx_fifo_underruns: 0
tx_stat_error: 0
rx_pcs_symbol_err: 0

-- enp193s0f1np1 --
[0]: rx_errors: 0
[0]: tx_errors: 0
[0]: rx_tpa_errors: 0
[0]: rx_l4_csum_errors: 0
[0]: rx_buf_errors: 0
[1]: rx_errors: 0
[1]: tx_errors: 0
[1]: rx_tpa_errors: 0
[1]: rx_l4_csum_errors: 0
[1]: rx_buf_errors: 0
[2]: rx_errors: 0
[2]: tx_errors: 0
[2]: rx_tpa_errors: 0
[2]: rx_l4_csum_errors: 0
[2]: rx_buf_errors: 0
[3]: rx_errors: 0
[3]: tx_errors: 0
[3]: rx_tpa_errors: 0
[3]: rx_l4_csum_errors: 0
[3]: rx_buf_errors: 0
[4]: rx_errors: 0
[4]: tx_errors: 0
[4]: rx_tpa_errors: 0
[4]: rx_l4_csum_errors: 0
[4]: rx_buf_errors: 0
[5]: rx_errors: 0
[5]: tx_errors: 0
[5]: rx_tpa_errors: 0
[5]: rx_l4_csum_errors: 0
[5]: rx_buf_errors: 0
[6]: rx_errors: 0
[6]: tx_errors: 0
[6]: rx_tpa_errors: 0
[6]: rx_l4_csum_errors: 0
[6]: rx_buf_errors: 0
[7]: rx_errors: 0
[7]: tx_errors: 0
[7]: rx_tpa_errors: 0
[7]: rx_l4_csum_errors: 0
[7]: rx_buf_errors: 0
rx_fcs_err_frames: 0
rx_align_err_frames: 0
rx_mtu_err_frames: 0
rx_stat_err: 0
tx_fcs_err_frames: 0
tx_err: 0
tx_fifo_underruns: 0
tx_stat_error: 0
rx_pcs_symbol_err: 0

-- enp193s0f2np2 --
[0]: rx_errors: 0
[0]: tx_errors: 0
[0]: rx_tpa_errors: 0
[0]: rx_l4_csum_errors: 0
[0]: rx_buf_errors: 0
[1]: rx_errors: 0
[1]: tx_errors: 0
[1]: rx_tpa_errors: 0
[1]: rx_l4_csum_errors: 0
[1]: rx_buf_errors: 0
[2]: rx_errors: 0
[2]: tx_errors: 0
[2]: rx_tpa_errors: 0
[2]: rx_l4_csum_errors: 0
[2]: rx_buf_errors: 0
[3]: rx_errors: 0
[3]: tx_errors: 0
[3]: rx_tpa_errors: 0
[3]: rx_l4_csum_errors: 0
[3]: rx_buf_errors: 0
[4]: rx_errors: 0
[4]: tx_errors: 0
[4]: rx_tpa_errors: 0
[4]: rx_l4_csum_errors: 0
[4]: rx_buf_errors: 0
[5]: rx_errors: 0
[5]: tx_errors: 0
[5]: rx_tpa_errors: 0
[5]: rx_l4_csum_errors: 0
[5]: rx_buf_errors: 0
[6]: rx_errors: 0
[6]: tx_errors: 0
[6]: rx_tpa_errors: 0
[6]: rx_l4_csum_errors: 0
[6]: rx_buf_errors: 0
[7]: rx_errors: 0
[7]: tx_errors: 0
[7]: rx_tpa_errors: 0
[7]: rx_l4_csum_errors: 0
[7]: rx_buf_errors: 0
rx_fcs_err_frames: 0
rx_align_err_frames: 0
rx_mtu_err_frames: 0
rx_stat_err: 0
tx_fcs_err_frames: 0
tx_err: 0
tx_fifo_underruns: 0
tx_stat_error: 0
rx_pcs_symbol_err: 0

-- enp193s0f3np3 --
[0]: rx_errors: 0
[0]: tx_errors: 0
[0]: rx_tpa_errors: 0
[0]: rx_l4_csum_errors: 0
[0]: rx_buf_errors: 0
[1]: rx_errors: 0
[1]: tx_errors: 0
[1]: rx_tpa_errors: 0
[1]: rx_l4_csum_errors: 0
[1]: rx_buf_errors: 0
[2]: rx_errors: 0
[2]: tx_errors: 0
[2]: rx_tpa_errors: 0
[2]: rx_l4_csum_errors: 0
[2]: rx_buf_errors: 0
[3]: rx_errors: 0
[3]: tx_errors: 0
[3]: rx_tpa_errors: 0
[3]: rx_l4_csum_errors: 0
[3]: rx_buf_errors: 0
[4]: rx_errors: 0
[4]: tx_errors: 0
[4]: rx_tpa_errors: 0
[4]: rx_l4_csum_errors: 0
[4]: rx_buf_errors: 0
[5]: rx_errors: 0
[5]: tx_errors: 0
[5]: rx_tpa_errors: 0
[5]: rx_l4_csum_errors: 0
[5]: rx_buf_errors: 0
[6]: rx_errors: 0
[6]: tx_errors: 0
[6]: rx_tpa_errors: 0
[6]: rx_l4_csum_errors: 0
[6]: rx_buf_errors: 0
[7]: rx_errors: 0
[7]: tx_errors: 0
[7]: rx_tpa_errors: 0
[7]: rx_l4_csum_errors: 0
[7]: rx_buf_errors: 0
rx_fcs_err_frames: 0
rx_align_err_frames: 0
rx_mtu_err_frames: 0
rx_stat_err: 0
tx_fcs_err_frames: 0
tx_err: 0
tx_fifo_underruns: 0
tx_stat_error: 0
rx_pcs_symbol_err: 0

##
# errors (/sys)
k-shibata@vm2022-06-b[PRODUCTION]:~$ grep -v ^0$ /sys/class/net/enp193*/statistics/*err*
/sys/class/net/enp193s0f1np1/statistics/rx_missed_errors:559 ## no problem

##
# NIC infomation (ethtool)
##

k-shibata@vm2022-06-b[PRODUCTION]:~$ ethtool -i enp193s0f0np0
driver: bnxt_en
version: 5.15.0-113-generic
firmware-version: 216.4.16.8/pkg 216.0.333.11
expansion-rom-version:
bus-info: 0000:c1:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

##
# Linux Kernel Version / Linux Distribution Version
##

k-shibata@vm2022-06-b[PRODUCTION]:~$ lsb_release -ir
Distributor ID: Ubuntu
Release: 22.04
k-shibata@vm2022-06-b[PRODUCTION]:~$ uname -a
Linux vm2022-06-b 5.15.0-113-generic #123-Ubuntu SMP Mon Jun 10 08:16:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

```

[Shiu202050]

Why no I use the Broadcom's NIC?

The Broadcom NIC is too small ringbufffer to our usage.
Its causes packet drop (receive) and packet requeue.
This is no good in production services.

I want to use Intel 25GbE NIC, but it's diffirectut the sensitive rx_error counter.

```

##
# Intel 25GbE NIC
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ ethtool -g enp193s0f0
Ring parameters for enp193s0f0:
Pre-set maximums:
RX: 8160
RX Mini: n/a
RX Jumbo: n/a
TX: 8160
Current hardware settings:
RX: 8160
RX Mini: n/a
RX Jumbo: n/a
TX: 8160

##
# Broadcom NIC
##

k-shibata@vm2022-06-b[PRODUCTION]:~$ ethtool -g enp193s0f0np0
Ring parameters for enp193s0f0np0:
Pre-set maximums:
RX: 2047
RX Mini: n/a
RX Jumbo: 8191
TX: 2047
Current hardware settings:
RX: 2047
RX Mini: n/a
RX Jumbo: 8188
TX: 2047

```

[Fikri_Intel]

Hi Shiu202050,

Thank you for your info.

Kindly allow us some time to check internally and revert back to you once info avaialable.

Regards,

Fikri O.

[Shiu202050]

Thank you.

[Amina_Sadiya]

Hello Team,

Thank you for your patience, To proceed further with your query I kindly request that you help us with the following details:

• Which type of the driver is currently use?
  • in-tree (shipped by OS vendor e.g. Red Hat, SLES, Ubuntu)
  • upstream mainline kernel (taken from git.kernel.org)
  • out of tree (taken from our GitHub https://github.com/intel/ethernet-linux-ice)
• What version of the driver is currently use?
• What type of driver (in-tree/upstream/out of tree) would you like to use in the future?

Best regards,

Amina

Intel Customer Support Technician

[ManoranjanDas]

Hello Shiu202050, 

Greeting for the Day! 

We are currently awaiting your response regarding the case. If you have any queries or require further assistance, please feel free to respond on the community post. We are more than happy to assist you. 

Thank you for choosing Intel products and services. 

Best regards, 

Manoranjan. 

Intel Customer Support Technician

[Shiu202050]

Hi

I already answered most questions.
See it: https://community.intel.com/t5/Ethernet-Products/ice-rx-errros-is-too-sensitive-to-IP-TCP-attack-packets-Intel/m-p/1668088#M40404

I will re-post the extracted information again.

##
# Linux Kernel Version / Linux Distribution Version
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ uname -a
Linux vm2022-06-a 5.15.0-76-generic #83-Ubuntu SMP Thu Jun 15 19:16:32 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

k-shibata@vm2022-06-a[PRODUCTION]:~$ lsb_release -ir
Distributor ID: Ubuntu
Release: 22.04

##
# NIC infomation (ethtool)
##

k-shibata@vm2022-06-a[PRODUCTION]:~$ ethtool -i enp193s0f0
driver: ice
version: 5.15.0-76-generic
firmware-version: 3.20 0x8000d833 1.3146.0
expansion-rom-version:
bus-info: 0000:c1:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

There is no difference between 5.15 and 6.13 in this part of the ice driver.

- https://github.com/torvalds/linux/blob/v6.13/drivers/net/ethernet/intel/ice/ice_txrx_lib.c#L122-L150
- https://github.com/torvalds/linux/blob/v6.13/drivers/net/ethernet/intel/ice/ice_main.c#L6976-L6990

The Linux kernel versions that we plan to use in the future are as follows:
- 5.15.0 (Ubuntu 22.04 LTS)
- 6.8.0 (Ubuntu 24.04 LTS)
- ?.?.? (Ubuntu 26.04 LTS)

I appreciate your cooperation. I'm really grateful for that.

However, I'm also busy with my work and don't have the time to get tired of asking the same questions over and over again. At least, I don't have enough time to monitor this thread on the fly.

[ManoranjanDas]

Hello Shiu202050, 

Greetings!

Apologies for the inconvenience caused.

Thank you for sharing the information. We are actively working with our internal team to resolve the issue. As soon as we receive an update from them, we'll be sure to keep you informed about the status.

Thank you for your understanding.

Best regards,

Manoranjan

Intel Customer Support Technician.

[Shiu202050]

Hello ManoranjanDas,

It's so sadly news.

I understand what you're trying to say, but there's little thing I can do about it.
I'm not allowed to do that during my work hours.

Since there is no other way, I'll consider looking into a non-Intel NIC.

Thank you for your assistance.

[Ragulan_Intel]

Hello Shiu202050,

Greetings!

We've sent an update to your email regarding your request. Since the update isn't relevant to others in the community, we decided not to post it in the public forum.

Please check your email, and if you need any further assistance, feel free to continue the conversation via email.

Best regards,

Ragulan_Intel

[Simon-Intel]

Hello Shiu202050,

Thank you for contacting Intel.

This is the second follow-up regarding the reported issue. We're eager to ensure a swift resolution and would appreciate any updates or additional information you can provide.

Please feel free to respond to this message at your earliest convenience.

Best regards,

Simon

Intel Customer Support Technician