From: Andrew Lunn <andrew@lunn.ch>
To: Frederic TOULBOT <ftoulbot@scaleway.com>
Cc: mkubecek@suse.cz, netdev@vger.kernel.org
Subject: Re: ethtool module info only reports hex info
Date: Thu, 16 May 2024 14:14:52 +0200 [thread overview]
Message-ID: <240d69aa-7f33-469f-8281-e254d5d0c85d@lunn.ch> (raw)
In-Reply-To: <CAAV7vNcRbVb00vp_u1q0f6jjqwVhx4GFAzWoP0AsRA1MhAfeBw@mail.gmail.com>
On Thu, May 16, 2024 at 09:23:05AM +0200, Frederic TOULBOT wrote:
> 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
Could you check it is being built with ETHTOOL_ENABLE_PRETTY_DUMP.
If you can build from source, maybe use gdb and check what is
happening in eeprom_parse()?
Andrew
next prev parent reply other threads:[~2024-05-16 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 7:23 ethtool module info only reports hex info Frederic TOULBOT
2024-05-16 12:14 ` Andrew Lunn [this message]
-- 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=240d69aa-7f33-469f-8281-e254d5d0c85d@lunn.ch \
--to=andrew@lunn.ch \
--cc=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