From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Priit Laes <plaes@plaes.org>
Cc: Jose Abreu <Jose.Abreu@synopsys.com>,
"linux-sunxi@googlegroups.com" <linux-sunxi@googlegroups.com>,
"wens@csie.org" <wens@csie.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"peppe.cavallaro@st.com" <peppe.cavallaro@st.com>,
"alexandre.torgue@st.com" <alexandre.torgue@st.com>
Subject: Re: sun7i-dwmac: link detection failure with 1000Mbit parters
Date: Fri, 1 Nov 2019 10:57:45 +0000 [thread overview]
Message-ID: <20191101105745.GJ25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191101094920.GB12834@plaes.org>
On Fri, Nov 01, 2019 at 09:49:20AM +0000, Priit Laes wrote:
> On Thu, Oct 31, 2019 at 10:38:41AM +0000, Russell King - ARM Linux admin wrote:
> > mii-diag -v eth0
> >
> > would be useful to see for the case where the link has failed, without
> > replugging the ethernet cable.
>
> mii-diag seems to be quite an useful tool, but unfortunately has not been
> packaged anymore on newer distro releases like Debian stable and latest
> Ubuntu LTS.
which is unfortunate because it's the best tool for debugging PHY
related problems. mii-tool doesn't dump registers, and dumping the
PHY registers is extremely useful.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-11-01 10:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 20:21 sun7i-dwmac: link detection failure with 1000Mbit parters Priit Laes
2019-10-31 8:39 ` Jose Abreu
2019-10-31 10:38 ` Russell King - ARM Linux admin
2019-11-01 9:49 ` Priit Laes
2019-11-01 10:57 ` Russell King - ARM Linux admin [this message]
2019-10-31 13:04 ` Andrew Lunn
2019-10-31 13:14 ` Andrew Lunn
2019-10-31 16:19 ` Priit Laes
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=20191101105745.GJ25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-sunxi@googlegroups.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=plaes@plaes.org \
--cc=wens@csie.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).