From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Martin Rowe <martin.p.rowe@gmail.com>,
netdev@vger.kernel.org, davem@davemloft.net,
vivien.didelot@gmail.com
Subject: Re: bug: net: dsa: mv88e6xxx: unable to tx or rx with Clearfog GT 8K (with git bisect)
Date: Sat, 11 Jul 2020 20:22:55 +0100 [thread overview]
Message-ID: <20200711192255.GO1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200711162349.GL1014141@lunn.ch>
On Sat, Jul 11, 2020 at 06:23:49PM +0200, Andrew Lunn wrote:
> So i'm guessing it is the connection between the CPU and the switch.
> Could you confirm this? Create a bridge, add two ports of the switch
> to the bridge, and then see if packets can pass between switch ports.
>
> If it is the connection between the CPU and the switch, i would then
> be thinking about the comphy and the firmware. We have seen issues
> where the firmware is too old. That is not something i've debugged
> myself, so i don't know where the version information is, or what
> version is required.
However, in the report, Martin said that reverting the problem commit
from April 14th on a kernel from July 6th caused everything to work
again. That is quite conclusive that 34b5e6a33c1a is the cause of
the breakage.
The question is how - I don't get it. None of the GT8k DSA ports are
fixed-links, not even the CPU port (which no longer even uses phylink.)
However, the MVPP2 is using a fixed-link on the port that faces the
DSA switch, which doesn't sound like a good idea to me to have
dis-similar configurations at either end. So the addition of
"|| mode == MLO_AN_FIXED" shouldn't make any difference.
I think some debug printks would be needed to work out what's going on.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-07-11 19:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 13:50 bug: net: dsa: mv88e6xxx: unable to tx or rx with Clearfog GT 8K (with git bisect) Martin Rowe
2020-07-11 16:23 ` Andrew Lunn
2020-07-11 19:22 ` Russell King - ARM Linux admin [this message]
2020-07-12 13:00 ` Martin Rowe
2020-07-12 13:25 ` Russell King - ARM Linux admin
2020-07-17 5:56 ` Martin Rowe
2020-07-17 9:21 ` Russell King - ARM Linux admin
2020-07-17 12:50 ` Martin Rowe
2020-07-17 18:51 ` Russell King - ARM Linux admin
2020-07-17 19:42 ` Andrew Lunn
2020-07-17 21:26 ` Russell King - ARM Linux admin
2020-07-18 2:37 ` Martin Rowe
2020-07-18 8:50 ` Russell King - ARM Linux admin
2020-07-18 9:43 ` Martin Rowe
2020-07-18 10:12 ` Russell King - ARM Linux admin
2020-07-18 11:21 ` Martin Rowe
2020-07-18 11:26 ` Russell King - ARM Linux admin
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=20200711192255.GO1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=martin.p.rowe@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.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 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).