netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Chris Healy <cphealy@gmail.com>
Cc: Marek Behun <marek.behun@nic.cz>, netdev <netdev@vger.kernel.org>
Subject: Re: bug: net: dsa: mv88e6xxx: serdes Unable to communicate on fiber with vf610-zii-dev-rev-c
Date: Sat, 18 Jul 2020 17:05:14 +0200	[thread overview]
Message-ID: <20200718150514.GC1375379@lunn.ch> (raw)
In-Reply-To: <CAFXsbZoMcOQTY8HE+E359jT6Vsod3LiovTODpjndHKzhTBZcTg@mail.gmail.com>

On Sat, Jul 18, 2020 at 07:49:26AM -0700, Chris Healy wrote:
> On Sat, Jul 18, 2020 at 7:42 AM Marek Behun <marek.behun@nic.cz> wrote:
> >
> > Hmm, nothing sticks out in the register dump.
> >
> > I encountered a similar problem 2 years ago on Topaz SERDES port when
> > the cmode was set to 2500BASE-X but the speed register was set to speed
> > incompatible with 2500BASE-X (I don't remember what, though). This
> > issue was solved by a patch I sent to netdev.
> >
> > Are you sure that your board isn't broken? Maybe the SerDes traces on
> > RX path are damaged...
> 
> In my case, both the SERDES and the MAC are inside the switch so I
> don't think it's likely that the SERDES traces are broken in there.
> If you are referring to the traces between the SERDES and the fiber
> module, that doesn't feel likely either as the SERDES appears to be
> reporting successfully received frames:
> 
> >From "ethtool -S" after sending 6 packets to the unit:
> serdes_rx_pkts: 6
> serdes_rx_bytes: 384
> serdes_rx_pkts_error: 0
> 
> If the traces were broken between the fiber module and the SERDES, I
> should not see these counters incrementing.

Plus it is reproducible on multiple boards, of different designs.

This is somehow specific to the 6390X ports 9 and 10.

     Andrew

  reply	other threads:[~2020-07-18 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18 14:27 bug: net: dsa: mv88e6xxx: serdes Unable to communicate on fiber with vf610-zii-dev-rev-c Chris Healy
2020-07-18 14:42 ` Marek Behun
2020-07-18 14:49   ` Chris Healy
2020-07-18 15:05     ` Andrew Lunn [this message]
2020-07-18 15:22       ` Marek Behun
2020-07-19 21:43         ` Chris Healy
2020-07-19 21:52           ` Marek Behun
2021-01-18 17:31           ` Tobias Waldekranz
2021-01-18 17:41             ` Andrew Lunn
2021-01-18 17:47               ` Tobias Waldekranz
2021-01-18 19:26                 ` Andrew Lunn

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=20200718150514.GC1375379@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=cphealy@gmail.com \
    --cc=marek.behun@nic.cz \
    --cc=netdev@vger.kernel.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).