From: Tobias Waldekranz <tobias@waldekranz.com>
To: Chris Healy <cphealy@gmail.com>, Marek Behun <marek.behun@nic.cz>
Cc: Andrew Lunn <andrew@lunn.ch>, netdev <netdev@vger.kernel.org>
Subject: Re: bug: net: dsa: mv88e6xxx: serdes Unable to communicate on fiber with vf610-zii-dev-rev-c
Date: Mon, 18 Jan 2021 18:31:19 +0100 [thread overview]
Message-ID: <8735yykv88.fsf@waldekranz.com> (raw)
In-Reply-To: <CAFXsbZrHRexg5zAsR1cah4p8HAZVc3tjKdMGKWO6Ha4jXux3QA@mail.gmail.com>
On Sun, Jul 19, 2020 at 14:43, Chris Healy <cphealy@gmail.com> wrote:
> On Sat, Jul 18, 2020 at 8:22 AM Marek Behun <marek.behun@nic.cz> wrote:
>>
>> On Sat, 18 Jul 2020 17:05:14 +0200
>> Andrew Lunn <andrew@lunn.ch> wrote:
>>
>> > > 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
>>
>> Hmm.
>>
>> What about the errata setup?
>> It says:
>> /* The 6390 copper ports have an errata which require poking magic
>> * values into undocumented hidden registers and then performing a
>> * software reset.
>> */
>> But then the port_hidden_write function is called for every port in the
>> function mv88e6390_setup_errata, not just for copper ports. Maybe Chris
>> should try to not write this hidden register for SerDes ports.
>
> I just disabled the mv88e6390_setup_errata all together and this did
> not result in any different behaviour on this broken fiber port.
Hi Chris,
Did you manage to track this down?
I am seeing the exact same issue. I have tried both a 1000base-x SFP and
a copper 1000base-T and get the same result on both - transmit is fine
but rx only works up to the SERDES, no rx MAC counters are moving.
next prev parent reply other threads:[~2021-01-18 17:32 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
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 [this message]
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=8735yykv88.fsf@waldekranz.com \
--to=tobias@waldekranz.com \
--cc=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).