[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250804160037.bqfb2cmwfay42zka@skbuf>
Date: Mon, 4 Aug 2025 19:00:37 +0300
From: Vladimir Oltean <vladimir.oltean@....com>
To: Alexander Wilhelm <alexander.wilhelm@...termo.com>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>,
Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Aquantia PHY in OCSGMII mode?
On Mon, Aug 04, 2025 at 04:47:03PM +0200, Alexander Wilhelm wrote:
> I’ve applied this patch as well, which brought me a step further. Unfortunately,
> I still don’t get a ping response, although the configuration looks correct to
> me. Below are the logs and the `ethtool` output I’m seeing:
>
> user@...t:~# logread | grep eth
> kern.info kernel: [ 20.777530] fsl_dpaa_mac ffe4e6000.ethernet: FMan MEMAC
> kern.info kernel: [ 20.782840] fsl_dpaa_mac ffe4e6000.ethernet: FMan MAC address: 00:00:5b:05:a2:cb
> kern.info kernel: [ 20.793126] fsl_dpaa_mac ffe4e6000.ethernet eth0: Probed interface eth0
> kern.info kernel: [ 31.058431] usbcore: registered new interface driver cdc_ether
> user.notice netifd: Added device handler type: veth
> kern.info kernel: [ 48.171837] fsl_dpaa_mac ffe4e6000.ethernet eth0: PHY [0x0000000ffe4fd000:07] driver [Aquantia AQR115] (irq=POLL)
> kern.info kernel: [ 48.171861] fsl_dpaa_mac ffe4e6000.ethernet eth0: configuring for phy/2500base-x link mode
> kern.info kernel: [ 48.181338] br-lan: port 1(eth0) entered blocking state
> kern.info kernel: [ 48.181363] br-lan: port 1(eth0) entered disabled state
> kern.info kernel: [ 48.181399] fsl_dpaa_mac ffe4e6000.ethernet eth0: entered allmulticast mode
> kern.info kernel: [ 48.181577] fsl_dpaa_mac ffe4e6000.ethernet eth0: entered promiscuous mode
> kern.info kernel: [ 53.304459] fsl_dpaa_mac ffe4e6000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
> kern.info kernel: [ 53.304629] br-lan: port 1(eth0) entered blocking state
> kern.info kernel: [ 53.304642] br-lan: port 1(eth0) entered forwarding state
> daemon.notice netifd: Network device 'eth0' link is up
> daemon.info lldpd[6849]: libevent 2.1.12-stable initialized with epoll method
> daemon.info charon: 10[KNL] flags changed for fe80::200:5bff:fe05:a2cb on eth0
>
> user@...t:~# ethtool eth0
> Settings for eth0:
> Supported ports: [ TP MII ]
> Supported link modes: 10baseT/Full
> 100baseT/Full
> 1000baseT/Full
> 2500baseT/Full
> Supported pause frame use: Symmetric Receive-only
> Supports auto-negotiation: Yes
> Supported FEC modes: Not reported
> Advertised link modes: 10baseT/Full
> 100baseT/Full
> 1000baseT/Full
> 2500baseT/Full
> Advertised pause frame use: Symmetric Receive-only
> Advertised auto-negotiation: Yes
> Advertised FEC modes: Not reported
> Link partner advertised link modes: 100baseT/Full
> 1000baseT/Full
> 10000baseT/Full
> 2500baseT/Full
> 5000baseT/Full
> Link partner advertised pause frame use: Symmetric Receive-only
> Link partner advertised auto-negotiation: Yes
> Link partner advertised FEC modes: Not reported
> Speed: 2500Mb/s
> Duplex: Full
> Port: Twisted Pair
> PHYAD: 7
> Transceiver: external
> Auto-negotiation: on
> MDI-X: on
> Current message level: 0x00002037 (8247)
> drv probe link ifdown ifup hw
> Link detected: yes
>
>
> I will continue investigating why the ping isn’t working and will share any new
> findings as soon as I have them. Thanks again for your support!
Can you apply the following patch, which adds support for ethtool
counters coming from the mEMAC, and dump them?
ethtool -S eth0 --groups eth-mac eth-phy eth-ctrl rmon | grep -v ': 0'
Could you then compare this to:
ethtool --phy-statistics eth0 | grep -v ': 0'
?
View attachment "0001-net-fman_memac-report-structured-ethtool-counters.patch" of type "text/x-diff" (7677 bytes)
Powered by blists - more mailing lists