From: Stephen Hemminger <stephen@networkplumber.org>
To: Rafa Corvillo <rafael.corvillo@aoifes.com>
Cc: netdev@vger.kernel.org
Subject: Re: [ISSUE: sky2 - rx error] Link stops working under heavy traffic load connected to a mv88e6176
Date: Tue, 25 Apr 2017 08:27:41 -0700 [thread overview]
Message-ID: <20170425082741.59428876@xeon-e3> (raw)
In-Reply-To: <58F9FD64.80506@aoifes.com>
On Fri, 21 Apr 2017 14:39:00 +0200
Rafa Corvillo <rafael.corvillo@aoifes.com> wrote:
> We are working in an ARMv7 embedded system running kernel 4.9 (LEDE build).
> It is an imx6 board with 2 ethernet interfaces. One of them is connected to
> a Marvell switch.
>
> The schema of the system is the following:
>
> +-------------------+ eth0
> | +--+
> | | |
> | Embedded system +--+
> | |
> | ARMv7 |
> | | Marvell 88E8057(sky2) +-------------+
> | +--+ +--+ +--+ eth1
> | | +---------------------+ | | +------+
> | +--+ CPU port +--+ mv88e6176 +--+
> +------+--+---------+ | |
> emulated| | | |
> GPIO +--+ +--+ +--+ eth2
> MDIO +-----------------------------------+ | | +------+
> MDIO +--+ +--+
> +-------------+
>
> There is a bridge (br-lan) which includes eth0/eth1/eth2
>
> If I connect the eth1/eth2, the link is up and I can do ping through it.
> But, once
> I start sending a heavy traffic load the link fails and the kernel sends the
> following messages:
>
> [ 48.557140] sky2 0000:04:00.0 marvell: rx error, status 0x5f20010
> length 1518
> [ 48.564964] sky2 0000:04:00.0 marvell: rx error, status 0x5f20010
> length 1518
> [ 48.572110] sky2 0000:04:00.0 marvell: rx error, status 0x5f20010
> length 1518
> [ 48.579263] sky2 0000:04:00.0 marvell: rx error, status 0x5f20010
> length 1518
> [ 48.586417] sky2 0000:04:00.0 marvell: rx error, status 0x5f20010
> length 1518
> [ 48.593573] sky2 0000:04:00.0 marvell: rx error, status 0x5f20010
> length 1518
> [ 48.600718] sky2 0000:04:00.0 marvell: rx error, status 0x5f20010
> length 1518
> [ 54.877567] net_ratelimit: 6 callbacks suppressed
> [ 54.882293] sky2 0000:04:00.0 marvell: rx error, status 0x5f20010
> length 1518
> [ 61.413552] sky2 0000:04:00.0 marvell: rx error, status 0x5f20010
> length 1518
The status error bits are in sky2.h
0x5f20010 is
05f2 frame length => 1522
0010 Too long err
That means the packet was longer than the configured MTU.
You are probably getting packets with VLAN tag but have not configured
a VLAN.
next prev parent reply other threads:[~2017-04-25 15:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 12:39 [ISSUE: sky2 - rx error] Link stops working under heavy traffic load connected to a mv88e6176 Rafa Corvillo
2017-04-24 6:45 ` Rafa Corvillo
2017-04-25 15:27 ` Stephen Hemminger [this message]
2017-04-27 12:05 ` Rafa Corvillo
2017-04-27 13:04 ` Andrew Lunn
2017-04-28 11:54 ` Rafa Corvillo
2017-04-28 12:22 ` Andrew Lunn
2017-05-08 12:03 ` Rafa Corvillo
2017-05-08 12:38 ` Andrew Lunn
2017-05-16 10:50 ` Rafa Corvillo
2017-05-16 12:47 ` Andrew Lunn
2017-05-16 13:09 ` Rafa Corvillo
2017-05-16 13:21 ` Andrew Lunn
2017-05-16 15:50 ` Rafa Corvillo
2017-05-16 15:58 ` Andrew Lunn
2017-05-16 16:19 ` Rafa Corvillo
2017-05-26 10:13 ` Rafa Corvillo
2017-05-31 19:31 ` 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=20170425082741.59428876@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=rafael.corvillo@aoifes.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