net: mv643xx: interface does not transmit after some time

6 messages, 4 authors, 2016-02-07 · open the first message on its own page

net: mv643xx: interface does not transmit after some time

From: Thomas Schlöter <hidden>
Date: 2016-02-06 18:24:50

Hello,

I am using mainline kernel 4.4 on a QNAP TS-412 (Marvell Kirkwood Feroceon 6281). The network interface mv643xx loses connection after a few minutes to some hours. Only bringing the interface down and up again helps.

Now I have a serial console for debugging. When I ping the dead interface and run ?watch ifconfig eth0? on the serial console, I can see the RX packets counting up while TX packets stays unchanged. Log files only show a message of some services showing a timeout or ?if_sendrawpacket: No buffer space available?.

How can I figure out what is wrong?

Regards,
Thomas

net: mv643xx: interface does not transmit after some time

From: andrew@lunn.ch (Andrew Lunn)
Date: 2016-02-06 18:34:14

How can I figure out what is wrong?
Hi Thomas

Can you find an easily way to reproduce it? iperf, or scp a big file
etc.

If you have a simple and reliable way to reproduce it, i would suggest
doing a git bisect to find out which change broke it.

      Andrew

net: mv643xx: interface does not transmit after some time

From: Martin Michlmayr <hidden>
Date: 2016-02-06 23:19:35

* Andrew Lunn [off-list ref] [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.

-- 
Martin Michlmayr
http://www.cyrius.com/

net: mv643xx: interface does not transmit after some time

From: Adam Baker <hidden>
Date: 2016-02-07 16:15:36

On 06/02/16 23:19, Martin Michlmayr wrote:
* Andrew Lunn [off-list ref] [2016-02-06 19:34]:
quoted
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.

Regards

Adam

net: mv643xx: interface does not transmit after some time

From: andrew@lunn.ch (Andrew Lunn)
Date: 2016-02-07 18:04:51

On Sun, Feb 07, 2016 at 04:15:36PM +0000, Adam Baker wrote:
On 06/02/16 23:19, Martin Michlmayr wrote:
quoted
* Andrew Lunn [off-list ref] [2016-02-06 19:34]:
quoted
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

net: mv643xx: interface does not transmit after some time

From: Thomas Schlöter <hidden>
Date: 2016-02-07 21:11:57

Am 07.02.2016 um 00:19 schrieb Martin Michlmayr [off-list ref]:
* Andrew Lunn [off-list ref] [2016-02-06 19:34]:
quoted
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
Sounds interesting. I will try that.
Hopefully Thomas can do a bisect.
I have never used that feature before. As far as I understand, I have to mark the last known good revision good and the most recent bad. Then I try every version in between which has changef related code. Right?

Actually I don't have a last good version as I had the original QNAP fw installed before.

4.3, which I installed during my first try was bad and 4.4 did not fix it. What can I do now? Should I provide my complete kernel config file?
At the moment I am trying Ian Campbell's patch as suggested by Andrew.

Thomas

@Martin: Sorry for reposting to your address, I did not manage to send plain text mail from my iPhone.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help