On Fri, 2014-10-31 at 14:29 +0100, Julien D'Ascenzio wrote:
Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit :
On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote:
You could inactivate this feature manually with:
ethtool -K eth0 tso off
I'm in contact with the
On Tue, 2014-11-04 at 08:51 +, Ian Campbell wrote:
On Fri, 2014-10-31 at 14:29 +0100, Julien D'Ascenzio wrote:
Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit :
On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote:
You could inactivate this feature manually with:
On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote:
You could inactivate this feature manually with:
ethtool -K eth0 tso off
I'm in contact with the developer of this feature. Tell me if this
command resolve your problem
Excellent, please let us know how you get on (feel free to
Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit :
On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote:
You could inactivate this feature manually with:
ethtool -K eth0 tso off
I'm in contact with the developer of this feature. Tell me if this
command resolve
Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit :
On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote:
You could inactivate this feature manually with:
ethtool -K eth0 tso off
I'm in contact with the developer of this feature. Tell me if this
command resolve
On Sun, 19 Oct 2014 14:44:11 +0200 Julien D'Ascenzio jdascen...@yahoo.fr
wrote:
Hi,
Since v3.16 kernel a tso feature was introduced in the driver of marvell
ethernet. This feature seems to work badly.
You could inactivate this feature manually with:
ethtool -K eth0 tso off
I'm in
Hi,
Since v3.16 kernel a tso feature was introduced in the driver of marvell
ethernet. This feature seems to work badly.
You could inactivate this feature manually with:
ethtool -K eth0 tso off
I'm in contact with the developer of this feature. Tell me if this
command resolve your problem
On Sun, 2014-10-19 at 14:44 +0200, Julien D'Ascenzio wrote:
Since v3.16 kernel a tso feature was introduced in the driver of marvell
ethernet. This feature seems to work badly.
3.16-1~exp1 was reported as not exhibiting the issue, but maybe that was
just a quick test which got lucky. So this
On Sun, 2014-10-12 at 23:46 +0200, Svenska wrote:
If you were able to try 3.16-1~exp1[0]
from snapshot.debian.org that might help rule that out.
I downloaded linux-image-3.16-trunk-kirkwood_3.16-1~exp1_armel.deb from
your link and flashed it into the NAS. I have not done a deeper
If you were able to try 3.16-1~exp1[0]
from snapshot.debian.org that might help rule that out.
I downloaded linux-image-3.16-trunk-kirkwood_3.16-1~exp1_armel.deb from
your link and flashed it into the NAS. I have not done a deeper
analysis, but it looks like the problem is gone.
For now, I
On Mon, 2014-10-06 at 01:21 +0200, Svenska wrote:
Package: src:linux
Version: 3.16.3-2
Severity: serious
Justification: may cause silent data corruption
Hello,
after upgrading the kernel of my NAS to 3.16-2-kirkwood, I noticed
corrupt data on my files. The NAS works as a DHCP client on
Package: src:linux
Version: 3.16.3-2
Severity: serious
Justification: may cause silent data corruption
Hello,
after upgrading the kernel of my NAS to 3.16-2-kirkwood, I noticed
corrupt data on my files. The NAS works as a DHCP client on its single
LAN port, the two hard drives run in a RAID1
12 matches
Mail list logo
