netdev - Re: bnxt_en: Invalid data read from SFP EEPROM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <d3c730cf-e629-48c0-a12e-19e1c7ea392e@lunn.ch>
Date: Fri, 25 Apr 2025 15:00:09 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Kamil Zaripov <zaripov-kamil@...ide.ai>
Cc: Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: bnxt_en: Invalid data read from SFP EEPROM

> Is there someone who can help me to find out where is the issue? The
> only bug that I find in code is that
> bnxt_read_sfp_module_eeprom_info do not fill bank_number field of
> the struct hwrm_port_phy_i2c_read_input, but it is not relevant for
> my case.

It could also be the SFP, or the cage. SFPs are notoriously buggy. I2C
needs a pull up resistors on the bus. If the SFP is contributing to
that resistance, it could be the overall resistance is too great in
this setup. Or the driving current is too low.

I've not looked at this driver. It is possible to influence the clock?
If you can slow it down and that makes it work, it points at the
hardware combination. The clock should be ticking at 100KHz, so try
50, 25, 10...

	Andrew