netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Martin Rowe <martin.p.rowe@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	vivien.didelot@gmail.com, linux@armlinux.org.uk
Subject: Re: bug: net: dsa: mv88e6xxx: unable to tx or rx with Clearfog GT 8K (with git bisect)
Date: Sat, 11 Jul 2020 18:23:49 +0200	[thread overview]
Message-ID: <20200711162349.GL1014141@lunn.ch> (raw)
In-Reply-To: <CAOAjy5T63wDzDowikwZXPTC5fCnPL1QbH9P1v+MMOfydegV30w@mail.gmail.com>

On Sat, Jul 11, 2020 at 01:50:21PM +0000, Martin Rowe wrote:
> Hello,
> 
> I hope this is the right forum.
> 
> I have been troubleshooting an issue with my Clearfog GT 8Ks where I
> am unable to tx or rx on the switch interface, which uses the
> mv88e6xxx driver. Based on git bisect, I believe it is related to
> commit 34b5e6a33c1a8e466c3a73fd437f66fb16cb83ea from around the
> 5.7-rc2 era.

Hi Martin

Thanks for the bug report.

> Symptoms:
> The interface used to work, then it stopped and I didn't immediately
> notice because of life. Now the network never comes fully up. dmesg
> indicates no issues bringing the device up. Links are brought up and
> down with cable connects and disconnects. Negotiation seems to be
> working. But the interface rx counter never increases. While the tx
> counters do increase, tcpdumps on the other end of the cables never
> see any traffic. Basically, it doesn't look like any traffic is going
> out or in.

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.

	Andrew

  reply	other threads:[~2020-07-11 16:23 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 [this message]
2020-07-11 19:22   ` Russell King - ARM Linux admin
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=20200711162349.GL1014141@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=linux@armlinux.org.uk \
    --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).