Bug#565404: linux-image-2.6.26-2-amd64: atl1e: TSO is broken
>>>>> "JY" == Jie Yang <Jie.Yang@Atheros.com> writes:
JY> Anders Boström <anders@netinsight.net> wrote:
>> Cc: ben@decadent.org.uk; netdev@vger.kernel.org;
>> 565404@bugs.debian.org; Xiong Huang
>> Subject: Re: Bug#565404: linux-image-2.6.26-2-amd64: atl1e:
>> TSO is broken
>> One strange observation is that I can only reproduce this
>> problem when transmitting data from a NFS-server using TCP
>> with Atheros AR8121/AR8113/AR8114.
>>
>> I've tried to reproduce the problem using test-programs, like
>> nttcp and netpipe, without any success. One observation is
>> that the test-programs *only* generates 1500 bytes
>> IP-packets. When the NFS-server sends data, a sequence of
>> 1500 bytes IP-packets are generated, ending with a shorter
>> packet. And this last packet in the sequence has 1500 in the
>> IP-header length field, but is shorter.
>>
JY> following is my test cese,
JY> a nfs server server with ar8131chip, device id 1063. export /tmp/ dir as the nfs share directory,
JY> the client, mount the server_ip:/tmp to local dir /mnt/nfs, ust a python script to write and read data on the
JY> /mnt/nfs/testnfs.log. it works fine.
OK, the device-ID in our NFS-server is 1026, rev. b0. So it is
possible that the problem is specific to that chip/version.
JY> Can you give me some advice on how to reproduce this bug??
The only suggestion I have is to try to find a board with a 1026-chip
on it.
My test-case is just copy of a 1 Gbyte file from the
NFS-server to /dev/null , after making sure that the file isn't cached
on the client by reading huge amounts of other data.
/ Anders
Reply to: