From: Frederic TOULBOT <ftoulbot@scaleway.com>
To: mkubecek@suse.cz, netdev@vger.kernel.org
Subject: ethtool module info only reports hex info
Date: Thu, 16 May 2024 09:23:05 +0200 [thread overview]
Message-ID: <CAAV7vNcRbVb00vp_u1q0f6jjqwVhx4GFAzWoP0AsRA1MhAfeBw@mail.gmail.com> (raw)
Hello, I have the impression that there is an unwanted change in the
output of the ethtool -m command with a certain QSFP type
I tested versions 6.5-1 / 5.16-1 / 5.4-1
The bug seems very close to this one
https://lists.openwall.net/netdev/2023/11/23/118
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
With ethtool 6.5-1 and 5.16-1
~# ethtool -m ens1f1
Offset Values
------ ------
0x0000: 11 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0010: 00 00 00 00 00 00 1d 0e 00 00 81 85 00 00 00 00
0x0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
And with version 5.4.1, we receive the expected result
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
dpkg -l ethtool
ii ethtool 1:5.4-1 amd64 display or change
Ethernet device settings
~# ethtool -m ens1f0
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 : 7db
Attenuation at 5.0GHz : 10db
Attenuation at 7.0GHz : 13db
Attenuation at 12.9GHz : 18db
Vendor name : CISCO-PUREOPTICS
Vendor OUI : 00:00:00
Vendor PN : QSFP-4SFP25G-CU2
Vendor rev : 6
Vendor SN : M9BE9185
Date code : 220412
Revision Compliance : SFF-8636 Rev 2.5/2.6/2.7
Module temperature : 29.05 degrees C / 84.30 degrees F
Module voltage : 3.3157 V
Alarm/warning flags implemented : Yes
Laser tx ...
next reply other threads:[~2024-05-16 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 7:23 Frederic TOULBOT [this message]
2024-05-16 12:14 ` ethtool module info only reports hex info Andrew Lunn
-- strict thread matches above, loose matches on Subject: below --
2023-11-23 7:42 Ivar Simensen
2023-11-23 11:29 ` Ido Schimmel
2023-11-24 9:33 ` Ivar Simensen
2023-11-23 15:19 ` Michal Kubecek
2023-11-24 7:38 ` Ivar Simensen
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=CAAV7vNcRbVb00vp_u1q0f6jjqwVhx4GFAzWoP0AsRA1MhAfeBw@mail.gmail.com \
--to=ftoulbot@scaleway.com \
--cc=mkubecek@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).