From: "Lluís Batlle i Rossell" <viric@viric.name>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"Carles Pagès" <page@cubata.homelinux.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Regarding tx-nocache-copy in the Sheevaplug
Date: Mon, 13 Oct 2014 16:31:38 +0200 [thread overview]
Message-ID: <20141013143138.GJ1972@vicerveza.homeunix.net> (raw)
In-Reply-To: <20141013142156.GE26864@lunn.ch>
Enabling tx offload and disabling tx-nocache-copy, making the machine *send* a
lot of ssh traffic (sftp for example) makes ssh fail HMAC. It's quite easy to
reproduce here.
As for the hardware, it's an old sheevaplug board.
On Mon, Oct 13, 2014 at 04:21:56PM +0200, Andrew Lunn wrote:
> On Mon, Oct 13, 2014 at 12:52:46PM +0200, Lluís Batlle i Rossell wrote:
> > Hello,
> >
> > on the 7th of January 2014 ths patch was applied:
> > https://lkml.org/lkml/2014/1/7/307
> >
> > [PATCH v2] net: Do not enable tx-nocache-copy by default
> >
> > In the Sheevaplug (ARM Feroceon 88FR131 from Marvell) this made packets to be
> > sent corrupted. I think this machine has something special about the cache.
>
> Hi Lluís
>
> Please could you describe your test setup. I would like to try to
> reproduce the problem. I have a machine based on kirkwood 6282 and the
> same ethernet.
>
> Thanks
> Andrew
next prev parent reply other threads:[~2014-10-13 14:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 10:52 Regarding tx-nocache-copy in the Sheevaplug Lluís Batlle i Rossell
2014-10-13 12:26 ` Eric Dumazet
2014-10-13 12:32 ` Lluís Batlle i Rossell
2014-10-13 14:21 ` Andrew Lunn
2014-10-13 14:31 ` Lluís Batlle i Rossell [this message]
2014-10-13 14:49 ` Eric Dumazet
2014-10-13 15:48 ` Lluís Batlle i Rossell
2014-10-15 21:57 ` Benjamin Poirier
2014-10-15 22:45 ` Eric Dumazet
2014-10-16 17:34 ` Benjamin Poirier
2014-10-16 17:46 ` Lluís Batlle i Rossell
2014-10-17 20:55 ` Benjamin Poirier
2014-10-16 17:48 ` Eric Dumazet
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=20141013143138.GJ1972@vicerveza.homeunix.net \
--to=viric@viric.name \
--cc=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=page@cubata.homelinux.net \
/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).