-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-8.6.0
-
ethtool-5.13-2.el8_6
-
None
-
None
-
rhel-sst-network-drivers
-
ssg_networking
-
None
-
Dev ack
-
False
-
-
None
-
None
-
Pass
-
Manual
-
---
-
-
x86_64
-
None
Description of problem:
Running "ethtool -m eth0" on a AMD/Pensando DSC does not work as expected. It also does not work on other vendor NICs that I have tried. When running the same command using Ethtool v5.12 or Ethtool v5.8 it works as expected.
Version-Release number of selected component (if applicable):
Ethtool: v5.13
RHEL8.6
How reproducible:
100%
Steps to Reproduce:
1. Run ethtool command to get module eeprom dump
ethtool -m eth0
netlink error: Invalid argument
Actual results:
Ethtool seems to correctly get the module eeprom len (for our case it's 256B), but fails when trying to actually get the module eeprom dump.
ethtool -m eth0
netlink error: Invalid argument
Expected results:
The following results were seen with Ethtool v5.12 from kernel.org on RHEL8.6:
ethtool -m eth0
Identifier : 0x11 (QSFP28)
Extended identifier : 0x10
Extended identifier description : 1.5W max. Power consumption
Extended identifier description : No CDR in TX, No CDR in RX
Extended identifier description : High Power Class (> 3.5 W) not enabled
Connector : 0x23 (No separable connector)
Transceiver codes : 0x80 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Transceiver type : 100G Ethernet: 100G Base-CR4 or 25G Base-CR CA-L
Encoding : 0x05 (64B/66B)
BR, Nominal : 25500Mbps
Rate identifier : 0x00
Length (SMF,km) : 0km
Length (OM3 50um) : 0m
Length (OM2 50um) : 0m
Length (OM1 62.5um) : 0m
Length (Copper or Active cable) : 2m
Transmitter technology : 0xa0 (Copper cable unequalized)
Attenuation at 2.5GHz : 4db
Attenuation at 5.0GHz : 6db
Attenuation at 7.0GHz : 8db
Attenuation at 12.9GHz : 11db
Vendor name : FS
Vendor OUI : 00:00:00
Vendor PN : Q28-PC02
Vendor rev : 5
Vendor SN : G1912206800
Date code : 191231
Revision Compliance : SFF-8636 Rev 2.5/2.6/2.7
Module temperature : 45.37 degrees C / 113.67 degrees F
Module voltage : 3.3140 V
Alarm/warning flags implemented : No
Laser tx bias current (Channel 1) : 0.000 mA
Laser tx bias current (Channel 2) : 0.000 mA
Laser tx bias current (Channel 3) : 0.000 mA
Laser tx bias current (Channel 4) : 0.000 mA
Transmit avg optical power (Channel 1) : 0.0000 mW / -inf dBm
Transmit avg optical power (Channel 2) : 0.0000 mW / -inf dBm
Transmit avg optical power (Channel 3) : 0.0000 mW / -inf dBm
Transmit avg optical power (Channel 4) : 0.0000 mW / -inf dBm
Receiver signal OMA(Channel 1) : 0.0000 mW / -inf dBm
Receiver signal OMA(Channel 2) : 0.0000 mW / -inf dBm
Receiver signal OMA(Channel 3) : 0.0000 mW / -inf dBm
Receiver signal OMA(Channel 4) : 0.0000 mW / -inf dBm
Additional info:
It looks like there was support for netlink based "ethtool -m" added right before Ethtool v5.13 was release. I'm wondering if this is the cause of the issue.
8b8cb55 (tag: v5.13) build: add list.h to file list in Makefile.am
799146b Release version 5.13.
601ea40 netlink: work around spurious selftest failure
4c8f9e3 Merge branch 'review/getmodule-v4' into master
79c8b58 ethtool: Update manpages to reflect changes to getmodule (-m) command
b2b1924 ethtool: Rename QSFP-DD identifiers to use CMIS
fc47fdb ethtool: Refactor human-readable module EEPROM output for new API
25b64c6 ethtool: Add netlink handler for getmodule (-m)
- external trackers