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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DFxJSK=XP5OwRy0_osU+UUs3bqjhT2ZT3RdNttv1Mo4g@mail.gmail.com>
Date: Thu, 13 Nov 2025 19:25:23 -0300
From: Fabio Estevam <festevam@...il.com>
To: Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>, 
	Russell King - ARM Linux <linux@...linux.org.uk>
Cc: edumazet <edumazet@...gle.com>, netdev <netdev@...r.kernel.org>
Subject: LAN8720: RX errors / packet loss when using smsc PHY driver on i.MX6Q

Hi,

On a custom i.MX6Q-based board using a LAN8720 PHY, we are observing
consistent packet loss when the LAN8720-specific PHY driver
(drivers/net/phy/smsc.c) is in use.

Kernel versions tested: 6.18-rc4 and 6.12
MAC driver: FEC (i.MX6)
PHY: LAN8720 (RMII) providing the 50 MHz ENET_REF clock to the SoC.

Behavior:

- Packet loss occurs when the LAN8720 is bound to the smsc PHY driver.

- No packet loss when using the generic PHY driver.

- No packet loss when the smsc driver is used and the link is forced
to 10 Mbps using ethtool.

The issue is easily reproduced with:

ping -c 1000 -i 0.2 -s 1300 <board-ip>

The board’s relevant DT fragment:

&fec {
    status = "okay";
    pinctrl-names = "default";
    pinctrl-0 = <&pinctrl_fec>;

    /* FEC ENET REF clock comes from LAN8720 */
    clocks = <&clks IMX6QDL_CLK_ENET>,
             <&clks IMX6QDL_CLK_ENET>,
             <&clks IMX6QDL_CLK_ENET>,
             <&clks IMX6QDL_CLK_ENET_REF>;
    clock-names = "ipg", "ahb", "ptp", "enet_out";

    phy-mode = "rmii";
    phy-reset-gpios = <&gpio2 4 GPIO_ACTIVE_LOW>;
    phy-reset-duration = <100>;
    phy-handle = <&ethphy0>;

    mdio {
        #address-cells = <1>;
        #size-cells = <0>;
        status = "okay";

        ethphy0: ethernet-phy@0 {
            reg = <0>;
            compatible = "ethernet-phy-ieee802.3-c22";
            max-speed = <100>;
            smsc,disable-energy-detect;
        };
    };
};

Has anyone seen similar behavior with LAN8720 or the smsc PHY driver
on i.MX platforms?
Any guidance on how to further debug this or what additional
information would be useful is appreciated.

Thanks,

Fabio Estevam

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ