From: Dario Alcocer <dalcocer@helixd.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org
Subject: Re: Marvell switch port shows LOWERLAYERDOWN, ping fails
Date: Wed, 28 Jul 2021 13:54:15 -0700 [thread overview]
Message-ID: <afed8a23-de6b-bcf2-e87f-8b68113abca5@helixd.com> (raw)
In-Reply-To: <YQHCSxgraGsXsz0J@lunn.ch>
On 7/28/21 1:47 PM, Andrew Lunn wrote:
>> Many thanks for the link; I will build and install it on the target. Hope it
>> will work with the older kernel (5.4.114) we're using.
>
> Probably not. You need
>
> commit b71a8d60252111d89dccba92ded7470faef16460
> Author: Andrew Lunn <andrew@lunn.ch>
> Date: Sun Oct 4 18:12:57 2020 +0200
>
> net: dsa: mv88e6xxx: Add per port devlink regions
>
> Add a devlink region to return the per port registers.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> 5.4 we released in 2019-11-24.
>
> When debugging issues like this, you really should be using a modern
> kernel. At minimum 5.13, better still, net-next.
You're absolutely right. The issue is we're relying on the upstream
socfpga Cyclone V kernel, and our custom board requires we rebase our
local fixes.
But, you're right: using net-next is probably what I try next, if commit
b71a8d6025 doesn't resolve this issue.
Thank you very much for all of the feedback!
next prev parent reply other threads:[~2021-07-28 20:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 22:55 Marvell switch port shows LOWERLAYERDOWN, ping fails Dario Alcocer
2021-07-23 13:41 ` Andrew Lunn
2021-07-23 18:21 ` Dario Alcocer
2021-07-23 18:25 ` Andrew Lunn
2021-07-23 18:36 ` Dario Alcocer
2021-07-23 21:58 ` Dario Alcocer
2021-07-24 17:34 ` Andrew Lunn
2021-07-25 2:26 ` Dario Alcocer
2021-07-25 2:36 ` Dario Alcocer
2021-07-27 1:39 ` Dario Alcocer
2021-07-28 18:07 ` Dario Alcocer
2021-07-28 18:23 ` Andrew Lunn
2021-07-28 18:33 ` Dario Alcocer
2021-07-28 19:24 ` Andrew Lunn
2021-07-28 19:37 ` Dario Alcocer
2021-07-28 20:47 ` Andrew Lunn
2021-07-28 20:54 ` Dario Alcocer [this message]
2021-07-28 21:09 ` Andrew Lunn
2021-08-05 21:44 ` Dario Alcocer
2021-08-06 16:03 ` Dario Alcocer
2021-08-06 23:46 ` Dario Alcocer
2021-08-07 18:57 ` Andrew Lunn
2021-08-09 16:28 ` Dario Alcocer
2021-08-10 20:58 ` Dario Alcocer
2021-08-10 22:13 ` Andrew Lunn
2021-08-11 13:16 ` Dario Alcocer
2021-08-07 17:44 ` 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=afed8a23-de6b-bcf2-e87f-8b68113abca5@helixd.com \
--to=dalcocer@helixd.com \
--cc=andrew@lunn.ch \
--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).