ethtool -m produces unreadable output for devices managed by the Intel ice driver

[Joshua Sjoding]

We have a Supermicro X12SDV-8C-SP6F motherboard with a pair of SFP28 ports managed by an Intel E823-L for SFP controller. On this machine the SFP28 ports are eno3 and eno4.

When asking ethtool for information about the installed SFP modules, we get this unhelpful output on Ubuntu Server 22.04 LTS:

sudo ethtool --module-info eno3
Offset Values
------ ------
0x0000: 03 04 07 20 00 00 02 00 00 00 00 06 67 02 0a 64
0x0010: 00 00 00 00 46 53 20 20 20 20 20 20 20 20 20 20
0x0020: 20 20 20 20 00 00 1b 21 53 46 50 2d 31 30 47 4c
0x0030: 52 2d 33 31 20 20 20 20 41 20 20 20 05 1e 00 d3
0x0040: 00 3a 00 00 46 32 30 33 30 33 32 32 36 38 39 20
0x0050: 20 20 20 20 32 32 30 34 30 32 20 20 68 fa 02 f1
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

I suspect this is the same bug that was reported by Red Hat here (access requires a Red Hat account):
https://access.redhat.com/solutions/6999793

This patch in netdev seems relevant:
https://<email address hidden>/T/

If I understand that patch correctly, this might a netdev issue that was exposed by a change in ethtool. If that's the case, then it's possible this shouldn't be classified as an ethtool bug, but I figured I'd start here.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ethtool 1:5.16-1
ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98
Uname: Linux 5.15.0-72-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri May 26 17:29:58 2023
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
SourcePackage: ethtool
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 May 27 01:43 seq
 crw-rw---- 1 root audio 116, 33 May 27 01:43 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-05-25 (2 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-E300-12D-8CN6P
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-72-generic root=UUID=b7ac1431-c6b1-4cef-af60-2626e4d6aab4 ro
ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-72-generic N/A
 linux-backports-modules-5.15.0-72-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: jammy
Uname: Linux 5.15.0-72-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 02/08/2023
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X12SDV-8C-SP6F
dmi.board.vendor: Supermicro
dmi.board.version: 1.10
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.2:bd02/08/2023:br5.24:svnSupermicro:pnSYS-E300-12D-8CN6P:pvr0123456789:rvnSupermicro:rnX12SDV-8C-SP6F:rvr1.10:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.:
dmi.product.family: Family
dmi.product.name: SYS-E300-12D-8CN6P
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

[Ben Hutchings (benh-debian)]

As suggested, this is indeed a bug in the ice kernel driver and not ethtool. Fixed by:

commit 84cba1840e68430325ac133a11be06bfb2f7acd8
Author: Petr Oros <email address hidden>
Date: Wed Mar 1 21:47:07 2023 +0100

    ice: copy last block omitted in ice_get_module_eeprom()

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2020917

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

apport information

[Joshua Sjoding (joshua.sjoding)]

It looks like installation of this update may have resolved the issue on our systems:

ethtool/jammy-updates 1:5.16-1ubuntu0.1

I believe that release was put together as a result of this bug report, which may or may not be a duplicate:

https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/2043983

[Joshua Sjoding (joshua.sjoding)]

I just went back to another machine that doesn't have "ethtool/jammy-updates 1:5.16-1ubuntu0.1" installed yet. It also produces correct output when I run "sudo ethtool --module-info eno3" now.

I think it's likely that this issue was fixed by some previous release and I just didn't notice it until today.