From: mk@drkrebs.de (Markus Krebs)
To: linux-arm-kernel@lists.infradead.org
Subject: Network timing (?) problems since kernel 3.12
Date: Sun, 09 Nov 2014 17:56:37 +0100 [thread overview]
Message-ID: <545F9CC5.6070709@drkrebs.de> (raw)
In-Reply-To: <20141109155502.GA10013@lunn.ch>
Am 09.11.2014 um 16:55 schrieb Andrew Lunn:
>> I'm using a Sheevaplug (Marvell Kirkwood) with an USB-Stick for
>> storage as a server. Since kernel 3.12 I'm experiencing various
>> erratic problems when transferring files, especially large or many
>> files at the same time, over the network (ssh complaining about
>> "Corrupted MAC on input" or Windows [over Samba] about corrupt
>> files).
>> Turning "offload check summing" off with ethtool didn't really help.
>
> Try turning off gso.
Thanks, Andrew; I've tried now but that didn't do the trick either.
next prev parent reply other threads:[~2014-11-09 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 15:15 Network timing (?) problems since kernel 3.12 Markus Krebs
2014-11-09 15:55 ` Andrew Lunn
2014-11-09 16:56 ` Markus Krebs [this message]
2014-11-12 19:48 ` Simon Baatz
2014-11-12 20:30 ` Markus Krebs
2014-11-14 15:01 ` Markus Krebs
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=545F9CC5.6070709@drkrebs.de \
--to=mk@drkrebs.de \
--cc=linux-arm-kernel@lists.infradead.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).