From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: "Eric Dumazet" <eric.dumazet@gmail.com>,
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: Fri, 17 Oct 2014 13:55:30 -0700 [thread overview]
Message-ID: <20141017205530.GA7367@f1.synalogic.ca> (raw)
In-Reply-To: <20141016174628.GL1972@vicerveza.homeunix.net>
On 2014/10/16 19:46, Lluís Batlle i Rossell wrote:
[...]
>
> Hello all,
>
> it seems I was a bit wrong - although enabling back tx-nocache-copy makes the
> tx-errors happen much less often (ssh complaining about HMAC), they still
> happen. It seems that something was introduced in some recent kernels that broke
> the tx offload.
>
> I have no idea what it can be, but since 2.6 until at least 3.10 the network
> driver worked fine with tx offload in this sheevaplug board.
It's not the most pleasant alternative but if you can be sure enough
whether the problem is occurring or not, you could try bisecting,
possibly limiting the bisection to mv643xx
$ git bisect start v3.16.3 v3.10 -- drivers/net/ethernet/marvell/mv643xx_eth.c
Bisecting: 16 revisions left to test after this (roughly 4 steps)
The problem might be outside of the driver though.
next prev parent reply other threads:[~2014-10-17 20:55 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
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 [this message]
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=20141017205530.GA7367@f1.synalogic.ca \
--to=benjamin.poirier@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=page@cubata.homelinux.net \
--cc=viric@viric.name \
/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).