Bug#961130: ethtool can read DOM values
On Thu, 2020-05-21 at 11:22 +0200, Bjørn Mork wrote: > Ben Hutchings writes: > > On Wed, 2020-05-20 at 13:09 +, Yannis Aribaud wrote: > > > Package: ethtool > > > Version: 1:4.19-1 > > > Severity: important > > > The command ethtool -m is unable to read the transceiver DOM values. > > > > Again, this is a driver or hardware issue, not a bug in ethtool. > > > > [...] > > > As you can see all mesuring values are zeros. > > > I am using Debian GNU/Linux 10 (buster), kernel 4.19.0-9-amd64 #1 SMP > > > Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux and libc6 2.28-10 > > > > > > FYI, I get correct values using SystemRescueCD 6 (ethtool 5.0, kernel > > > 4.19.34-1-lts) on this same hardware, using the same command. > > > > I see no changes to ethtool between 4.19 and 5.0 that would explain > > that. > > I assume you're aware of this, but there are some interesting changes in > that driver between v4.19.34 and v4.19.118 I actually hadn't looked yet, so thanks for doing that. > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=7da11d6a5d85ab3f4d28fa660d8c90566fdaa1e6 > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=935f39807a7e95678e5bda50757af326691a211c > > > The net effect seems to be that they removed the part that actually made > DOM reading work. Yes, these patches don't make sense. If only the real EEPROM is readable then the correct fix would be to change both type and size to the SFF-8079 values. > Makes me wonder what happens if you revert both those > patches? I don't have the hardware, so I can't test.. > > This issue might also be fixed in mainline with the more generic high > page support for QSFP28 and QSFP+? I don't know, I no longer keep track of networking stuff beyond what I read in LWN. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Bug#961130: ethtool can read DOM values
Ben Hutchings writes: > On Wed, 2020-05-20 at 13:09 +, Yannis Aribaud wrote: >> Package: ethtool >> Version: 1:4.19-1 >> Severity: important >> The command ethtool -m is unable to read the transceiver DOM values. > > Again, this is a driver or hardware issue, not a bug in ethtool. > > [...] >> As you can see all mesuring values are zeros. >> I am using Debian GNU/Linux 10 (buster), kernel 4.19.0-9-amd64 #1 SMP >> Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux and libc6 2.28-10 >> >> FYI, I get correct values using SystemRescueCD 6 (ethtool 5.0, kernel >> 4.19.34-1-lts) on this same hardware, using the same command. > > I see no changes to ethtool between 4.19 and 5.0 that would explain > that. I assume you're aware of this, but there are some interesting changes in that driver between v4.19.34 and v4.19.118 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=7da11d6a5d85ab3f4d28fa660d8c90566fdaa1e6 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=935f39807a7e95678e5bda50757af326691a211c The net effect seems to be that they removed the part that actually made DOM reading work. Makes me wonder what happens if you revert both those patches? I don't have the hardware, so I can't test.. This issue might also be fixed in mainline with the more generic high page support for QSFP28 and QSFP+? Bjørn
Processed: Re: Bug#961130: ethtool can read DOM values
Processing control commands: > reassign -1 src:linux 4.19.118-2 Bug #961130 [ethtool] ethtool can read DOM values Bug reassigned from package 'ethtool' to 'src:linux'. No longer marked as found in versions ethtool/1:4.19-1. Ignoring request to alter fixed versions of bug #961130 to the same values previously set Bug #961130 [src:linux] ethtool can read DOM values Marked as found in versions linux/4.19.118-2. -- 961130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961130: ethtool can read DOM values
Control: reassign -1 src:linux 4.19.118-2 On Wed, 2020-05-20 at 13:09 +, Yannis Aribaud wrote: > Package: ethtool > Version: 1:4.19-1 > Severity: important > The command ethtool -m is unable to read the transceiver DOM values. Again, this is a driver or hardware issue, not a bug in ethtool. [...] > As you can see all mesuring values are zeros. > I am using Debian GNU/Linux 10 (buster), kernel 4.19.0-9-amd64 #1 SMP > Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux and libc6 2.28-10 > > FYI, I get correct values using SystemRescueCD 6 (ethtool 5.0, kernel > 4.19.34-1-lts) on this same hardware, using the same command. I see no changes to ethtool between 4.19 and 5.0 that would explain that. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Bug#961130: ethtool can read DOM values
Package: ethtool Version: 1:4.19-1 Severity: important The command ethtool -m is unable to read the transceiver DOM values. Here is a transcript: root@localhost:~# ethtool -i ens2f0 driver: mlx5_core version: 5.0-0 firmware-version: 14.25.8000 (DEL2420110034) expansion-rom-version: bus-info: :65:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes root@localhost:~# ethtool -m ens2f0 Identifier : 0x03 (SFP) Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID) Connector : 0x07 (LC) Transceiver codes : 0x10 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Transceiver type : 10G Ethernet: 10G Base-SR Encoding : 0x06 (64B/66B) BR, Nominal : 10300MBd Rate identifier : 0x00 (unspecified) Length (SMF,km) : 0km Length (SMF) : 0m Length (50um) : 80m Length (62.5um) : 20m Length (Copper) : 0m Length (OM3) : 300m Laser wavelength : 850nm Vendor name : Pureoptics Vendor OUI : 00:00:00 Vendor PN : EX-SFP-10GE-SR Vendor rev : B4 Option values : 0x00 0x1a Option : RX_LOS implemented Option : TX_FAULT implemented Option : TX_DISABLE implemented BR margin, max : 0% BR margin, min : 0% Vendor SN : M4787212 Date code : 200222 Optical diagnostics support : Yes Laser bias current : 0.000 mA Laser output power : 0. mW / -inf dBm Receiver signal average optical power : 0. mW / -inf dBm Module temperature : 0.00 degrees C / 32.00 degrees F Module voltage : 0. V Alarm/warning flags implemented : Yes Laser bias current high alarm : Off Laser bias current low alarm : Off Laser bias current high warning : Off Laser bias current low warning : Off Laser output power high alarm : Off Laser output power low alarm : Off Laser output power high warning : Off Laser output power low warning : Off Module temperature high alarm : Off Module temperature low alarm : Off Module temperature high warning : Off Module temperature low warning : Off Module voltage high alarm : Off Module voltage low alarm : Off Module voltage high warning : Off Module voltage low warning : Off Laser rx power high alarm : Off Laser rx power low alarm : Off Laser rx power high warning : Off Laser rx power low warning : Off Laser bias current high alarm threshold : 0.000 mA Laser bias current low alarm threshold : 0.000 mA Laser bias current high warning threshold : 0.000 mA Laser bias current low warning threshold : 0.000 mA Laser output power high alarm threshold : 0. mW / -inf dBm Laser output power low alarm threshold : 0. mW / -inf dBm Laser output power high warning threshold : 0. mW / -inf dBm Laser output power low warning threshold : 0. mW / -inf dBm Module temperature high alarm threshold : 0.00 degrees C / 32.00 degrees F Module temperature low alarm threshold : 0.00 degrees C / 32.00 degrees F Module temperature high warning threshold : 0.00 degrees C / 32.00 degrees F Module temperature low warning threshold : 0.00 degrees C / 32.00 degrees F Module voltage high alarm threshold : 0. V Module voltage low alarm threshold : 0. V Module voltage high warning threshold : 0. V Module voltage low warning threshold : 0. V Laser rx power high alarm threshold : 0. mW / -inf dBm Laser rx power low alarm threshold : 0. mW / -inf dBm Laser rx power high warning threshold : 0. mW / -inf dBm Laser rx power low warning threshold : 0. mW / -inf dBm As you can see all mesuring values are zeros. I am using Debian GNU/Linux 10 (buster), kernel 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux and libc6 2.28-10 FYI, I get correct values using SystemRescueCD 6 (ethtool 5.0, kernel 4.19.34-1-lts) on this same hardware, using the same command. Regards,-- Yannis Aribaud
