From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: net: mv643xx: interface does not transmit after some time
Date: Sun, 7 Feb 2016 19:04:51 +0100 [thread overview]
Message-ID: <20160207180451.GA27070@lunn.ch> (raw)
In-Reply-To: <56B76DA8.3090500@baker-net.org.uk>
On Sun, Feb 07, 2016 at 04:15:36PM +0000, Adam Baker wrote:
> On 06/02/16 23:19, Martin Michlmayr wrote:
> >* Andrew Lunn <andrew@lunn.ch> [2016-02-06 19:34]:
> >>Can you find an easily way to reproduce it? iperf, or scp a big file
> >>etc.
> >
> >FWIW, we had a similar bug report in Debian recently:
> >https://lists.debian.org/debian-arm/2016/01/msg00098.html
> >
> >Turning off TCP RX and TX offloading make it go away:
> >https://lists.debian.org/debian-arm/2016/01/msg00100.html
> >
> >Hopefully Thomas can do a bisect.
> >
>
> I observed a similar issue when performing a large NFSv4 transfer
> with a kirkwood based server. Unfortunately I'd just jumped from
> 3.14 to 4.4 so I could do with a better starting point to bisect
> from.
>
> It failed several times while transferring a 4GB file over NFS but
> is stable in normal use.
I tried iperf, 6Gbytes, both RX and TX and it worked. This is with
4.5-rc2 net-next.
I will try again with different window sizes etc, to see if i can
trigger it.
Andrew
next prev parent reply other threads:[~2016-02-07 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 18:24 net: mv643xx: interface does not transmit after some time Thomas Schlöter
2016-02-06 18:34 ` Andrew Lunn
2016-02-06 23:19 ` Martin Michlmayr
2016-02-07 16:15 ` Adam Baker
2016-02-07 18:04 ` Andrew Lunn [this message]
[not found] ` <2ACB3A0B-DD51-43C1-A56E-E7C175645554@schloeter.net>
2016-02-07 20:35 ` Andrew Lunn
2016-02-07 21:07 ` Thomas Schlöter
2016-02-08 18:49 ` Thomas Schlöter
2016-02-10 18:40 ` Thomas Schlöter
2016-02-10 22:57 ` Andrew Lunn
2016-02-11 14:38 ` Ezequiel Garcia
2016-02-11 14:38 ` Ezequiel Garcia
2016-02-27 20:06 ` Adam Baker
2016-02-27 20:06 ` Adam Baker
2016-02-07 21:11 ` Thomas Schlöter
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=20160207180451.GA27070@lunn.ch \
--to=andrew@lunn.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.