From: "™֟☻̭҇ Ѽ ҉ ®" <vtolkm@googlemail.com>
To: netdev@vger.kernel.org
Cc: Vivien Didelot <vivien.didelot@gmail.com>, Andrew Lunn <andrew@lunn.ch>
Subject: Re: loss of connectivity after enabling vlan_filtering
Date: Tue, 14 Jan 2020 21:33:11 +0000 [thread overview]
Message-ID: <4af746cc-b86a-f083-49f7-558df05148bd@gmail.com> (raw)
In-Reply-To: <20190705132957.GB6495@t480s.localdomain>
On 05/07/2019 17:29, Vivien Didelot wrote:
> On Sun, 30 Jun 2019 01:23:02 +0200, vtolkm@googlemail.com wrote:
>> A simple soul might infer that mv88e6xxx includes MV88E6060, at least
>> that happened to me apparently (being said simpleton).
> I agree that is confusing, that is why I don't like the 'xxx' naming
> convention in general, found in many drivers. I'd prefer to stick with a
> reference model, or product category, like soho in this case. But it was
> initially written like this, so no reason to change its name now. I still
> plan to merge mv88e6060 into mv88e6xxx, but it is unfortunately low priority
> because I still don't have a platform with a 88E6060 on it.
>
> Thanks,
>
> Vivien
At long last discovered (accidentality) what causes the loss of
connectivity when enabling vlan_filtering, the node being dual-core and
each core providing a port facing the switchdev:
cpu0 - eht0 [RGMII] <--- > switchdev port 6
cpu1 - eth1 [RGMII] <--- > switchdev port 5
If only one of the CPU ports is connected to the respective switchdev
port connectivity to the node gets severed when enabling vlan_filtering.
With both CPU ports connected to the respective switchdev ports
connectivity remains uninterrupted to the node when enabling
vlan_filtering.
next prev parent reply other threads:[~2020-01-14 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 22:01 loss of connectivity after enabling vlan_filtering vtolkm
2019-06-29 22:49 ` Andrew Lunn
2019-06-29 23:04 ` vtolkm
2019-06-29 23:11 ` Andrew Lunn
2019-06-29 23:23 ` vtolkm
2019-06-30 0:37 ` vtolkm
2019-06-30 1:13 ` vtolkm
2019-06-30 7:46 ` vtolkm
2019-07-05 17:29 ` Vivien Didelot
2020-01-14 21:33 ` ™֟☻̭҇ Ѽ ҉ ® [this message]
2020-01-15 12:56 ` ™֟☻̭҇ Ѽ ҉ ®
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=4af746cc-b86a-f083-49f7-558df05148bd@gmail.com \
--to=vtolkm@googlemail.com \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vtolkm@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).