[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7nz6fvq6aaclh3xoazgqzw3kzc7vgmsufzyu4slsqhjht7dlpl@qyu63otcswga>
Date: Tue, 21 May 2024 09:34:42 +0200
From: Michal Kubecek <mkubecek@...e.cz>
To: Krzysztof Olędzki <ole@....pl>
Cc: Moshe Shemesh <moshe@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: "netlink error: Invalid argument" with ethtool-5.13+ on recent
kernels due to "ethtool: Add netlink handler for getmodule (-m)" -
25b64c66f58d3df0ad7272dda91c3ab06fe7a303, also no SFP-DOM support via
netlink?
On Tue, May 21, 2024 at 12:02:47AM -0700, Krzysztof Olędzki wrote:
> # ./ethtool --version
> ethtool version 6.7
>
> # ./ethtool --debug 3 -m eth3
[...]
> sending genetlink packet (76 bytes):
> msg length 76 ethool ETHTOOL_MSG_MODULE_EEPROM_GET
> received genetlink packet (96 bytes):
> msg length 96 error errno=-22
> netlink error: Invalid argument
Can you do it with "--debug 0x12" or "--debug 0x1e"? It would tell us
which request failed and that might give some hint where does this
EINVAL come from.
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists