[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141105100953.GA29022@magnum.frso.rivierawaves.com>
Date: Wed, 5 Nov 2014 11:09:53 +0100
From: Karl Beldan <karl.beldan@...il.com>
To: Ian Campbell <ijc@...lion.org.uk>
Cc: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
netdev@...r.kernel.org, David Miller <davem@...emloft.net>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Gregory Clement <gregory.clement@...e-electrons.com>,
Tawfik Bayouk <tawfik@...vell.com>,
Lior Amsalem <alior@...vell.com>,
Nadav Haklai <nadavh@...vell.com>, 764162@...s.debian.org
Subject: Re: [PATCH 0/1] mv643xx_eth: Disable TSO by default
On Wed, Nov 05, 2014 at 08:39:26AM +0000, Ian Campbell wrote:
> On Tue, 2014-11-04 at 15:20 +0100, Karl Beldan wrote:
> > On Sat, Nov 01, 2014 at 12:30:19PM -0300, Ezequiel Garcia wrote:
> > > Several users ([1], [2]) have been reporting data corruption with TSO on
> > > Kirkwood platforms (i.e. using the mv643xx_eth driver).
> > >
> > > Until we manage to find what's causing this, this simple patch will make
> > > the TSO path disabled by default. This patch should be queued for stable,
> > > fixing the TSO feature introduced in v3.16.
> > >
> > > The corruption itself is very easy to reproduce: checking md5sum on a mounted
> > > NFS directory gives a different result each time. Same tests using the mvneta
> > > driver (Armada 370/38x/XP SoC) pass with no issues.
> > >
> > > Frankly, I'm a bit puzzled about this, and so any ideas or debugging hints
> > > are well received.
> > >
> >
> > Hi,
> >
> > Can you try this :
>
> It fixes things for me, thanks!
>
> Tested-by: Ian Campbell <ijc@...lion.org.uk>
>
Good thing, thanks for your feedbak Ian !
Karl
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists