From: "Uwe Kleine-König" <uwe@kleine-koenig.org>
To: Arnaud Ebalard <arno@natisbad.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: netdev@vger.kernel.org
Subject: network unreliable on ReadyNAS 104 with Debian kernel
Date: Sat, 2 May 2020 16:14:08 +0200 [thread overview]
Message-ID: <20200502141408.GA29911@taurus.defre.kleine-koenig.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
Hello Arnaud, hello Thomas,
I own a ReadyNAS 104 (CPU: Armada 370, mvneta driver) and since some
time its network driver isn't reliable any more. I see things like:
$ rsync -a remotehost:dir /srv/dir
ssh_dispatch_run_fatal: Connection to $remoteaddress port 22: message authentication code incorrect
rsync: connection unexpectedly closed (11350078 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(235) [receiver=3.1.3]
rsync: connection unexpectedly closed (13675 bytes received so far) [generator]
rsync error: unexplained error (code 255) at io.c(235) [generator=3.1.3]
when ever something like this happens, I get
mvneta d0074000.ethernet eth1: bad rx status 0e8b0000 (overrun error), size=680
(with varying numbers after size=) in the kernel log.
With
sudo ethtool -K eth1 tso off gso off gro off
the behaviour gets better, but I still get errors. In tcpdump I saw
packets received that are a mix of (at least) two other packets sent on
the remote side.
This happens with Debian's 5.4.0-4-armmp (Version: 5.4.19-1) kernel, but
I also experienced it with the 4.19 series. On slow connections this
isn't a problem so the problem might exist already longer. In fact I
think there are two problems: The first is that the hardware doesn't get
enough buffers in time for the receive path and the other is that in the
error case corrupted packets are given to the upper layers.
Does this ring a bell for you? I didn't start to debug that yet.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-05-02 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 14:14 Uwe Kleine-König [this message]
2020-05-02 19:31 ` network unreliable on ReadyNAS 104 with Debian kernel Thomas Petazzoni
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=20200502141408.GA29911@taurus.defre.kleine-koenig.org \
--to=uwe@kleine-koenig.org \
--cc=arno@natisbad.org \
--cc=netdev@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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