From: Florian Fainelli <f.fainelli@gmail.com>
To: Ron Eggler <ron.eggler@mistywest.com>, Andrew Lunn <andrew@lunn.ch>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
netdev@vger.kernel.org,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: issues to bring up two VSC8531 PHYs
Date: Fri, 21 Apr 2023 17:09:50 -0700 [thread overview]
Message-ID: <e65a8575-8a76-4b09-c398-aee5272921a7@gmail.com> (raw)
In-Reply-To: <fa806e4a-b706-ce54-b3e0-b95d065e8d4a@mistywest.com>
On 4/21/2023 3:55 PM, Ron Eggler wrote:
>
> On 4/21/23 09:35, Andrew Lunn wrote:
>>>> You can also try:
>>>>
>>>> ethtool --phy-statistics ethX
>>> after appliaction of the above patch, ethtool tells me
>>>
>>> # ethtool --phy-statistics eth0
>>> PHY statistics:
>>> phy_receive_errors: 65535
>>> phy_idle_errors: 255
>> So these have saturated. Often these counters don't wrap, they stop at
>> the maximum value.
>>
>> These errors also indicate your problem is probably not between the
>> MAC and the PHY, but between the PHY and the RJ45 socket. Or maybe how
>> the PHY is clocked. It might not have a stable clock, or the wrong
>> clock frequency.
>
> The man page (https://www.man7.org/linux/man-pages/man8/ethtool.8.html)
> does not give any details about what phy_receive_errors or
> phy_idle_errors refer to exactly, is there any documentation about it
> that I could not find?
The statistics are inherently PHY specific and how a driver writer
choses to map a name to a specific PHY counter is backed within the driver.
--
Florian
next prev parent reply other threads:[~2023-04-22 0:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 20:11 issues to bring up two VSC8531 PHYs Ron Eggler
2023-04-12 22:10 ` Andrew Lunn
2023-04-12 22:12 ` Heiner Kallweit
2023-04-12 22:20 ` Andrew Lunn
2023-04-12 22:37 ` Heiner Kallweit
2023-04-13 20:13 ` Ron Eggler
2023-04-13 20:27 ` Andrew Lunn
2023-04-21 16:06 ` Ron Eggler
2023-04-21 16:35 ` Andrew Lunn
2023-04-21 22:55 ` Ron Eggler
2023-04-22 0:09 ` Florian Fainelli [this message]
2023-04-23 22:53 ` Ron Eggler
2023-04-22 0:28 ` Ron Eggler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e65a8575-8a76-4b09-c398-aee5272921a7@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=ron.eggler@mistywest.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.