All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Network Development <netdev@vger.kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: warnings from MTU setting on switch ports
Date: Mon, 30 Nov 2020 16:04:39 +0000	[thread overview]
Message-ID: <20201130160439.a7kxzaptt5m3jfyn@skbuf> (raw)
In-Reply-To: <b4adfc0b-cd48-b21d-c07f-ad35de036492@prevas.dk>

Hi Rasmus,

On Mon, Nov 30, 2020 at 03:30:50PM +0100, Rasmus Villemoes wrote:
> Hi,
>
> Updating our mpc8309 board to 5.9, we're starting to get
>
> [    0.709832] mv88e6085 mdio@e0102120:10: nonfatal error -34 setting MTU on port 0
> [    0.720721] mv88e6085 mdio@e0102120:10: nonfatal error -34 setting MTU on port 1
> [    0.731002] mv88e6085 mdio@e0102120:10: nonfatal error -34 setting MTU on port 2
> [    0.741333] mv88e6085 mdio@e0102120:10: nonfatal error -34 setting MTU on port 3
> [    0.752220] mv88e6085 mdio@e0102120:10: nonfatal error -34 setting MTU on port 4
> [    0.764231] eth1: mtu greater than device maximum
> [    0.769022] ucc_geth e0102000.ethernet eth1: error -22 setting MTU to include DSA overhead
>
> So it does say "nonfatal", but do we have to live with those warnings on
> every boot going forward, or is there something that we could do to
> silence it?
>
> It's a mv88e6250 switch with cpu port connected to a ucc_geth interface;
> the ucc_geth driver indeed does not implement ndo_change_mtu and has
> ->max_mtu set to the default of 1500.

To suppress the warning:

commit 4349abdb409b04a5ed4ca4d2c1df7ef0cc16f6bd
Author: Vladimir Oltean <olteanv@gmail.com>
Date:   Tue Sep 8 02:25:56 2020 +0300

    net: dsa: don't print non-fatal MTU error if not supported

    Commit 72579e14a1d3 ("net: dsa: don't fail to probe if we couldn't set
    the MTU") changed, for some reason, the "err && err != -EOPNOTSUPP"
    check into a simple "err". This causes the MTU warning to be printed
    even for drivers that don't have the MTU operations implemented.
    Fix that.

    Signed-off-by: Vladimir Oltean <olteanv@gmail.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

But you might also want to look into adding .ndo_change_mtu for
ucc_geth. If you are able to pass MTU-sized traffic through your
mv88e6085, then it is probably the case that the mpc8309 already
supports larger packets than 1500 bytes, and it is simply a matter of
letting the stack know about that. The warning is there to give people a
clue for the reason why MTU-sized traffic might not work over DSA.

  reply	other threads:[~2020-11-30 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 14:30 warnings from MTU setting on switch ports Rasmus Villemoes
2020-11-30 16:04 ` Vladimir Oltean [this message]
2020-11-30 22:13   ` Rasmus Villemoes
2020-11-30 22:35     ` Vladimir Oltean
2020-11-30 22:50       ` Rasmus Villemoes
2020-11-30 23:11       ` Andrew Lunn
2020-12-05 14:49     ` vlan_filtering=1 breaks all traffic (was: Re: warnings from MTU setting on switch ports) Rasmus Villemoes
2020-12-05 15:45       ` Russell King - ARM Linux admin
2020-12-05 16:02         ` vlan_filtering=1 breaks all traffic Rasmus Villemoes
2020-12-05 19:03       ` vlan_filtering=1 breaks all traffic (was: Re: warnings from MTU setting on switch ports) Vladimir Oltean
2020-12-05 20:13         ` vlan_filtering=1 breaks all traffic Rasmus Villemoes
2020-12-06 19:45           ` Vladimir Oltean
2020-12-07 19:43             ` Rasmus Villemoes
2020-12-07 20:15               ` Vladimir Oltean
2020-12-08  2:22                 ` 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=20201130160439.a7kxzaptt5m3jfyn@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rasmus.villemoes@prevas.dk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.