From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anders =?iso-8859-1?Q?Bostr=F6m?= Subject: Re: Bug#565404: linux-image-2.6.26-2-amd64: atl1e: TSO is broken Date: Tue, 02 Apr 2013 09:35:04 +0200 (CEST) Message-ID: <20130402.093504.1785848735327620554.anders@netinsight.net> References: <20100126.093439.651115405791675606.anders@netinsight.net> <1364689558.3557.22.camel@deadeye.wl.decadent.org.uk> Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Jie.Yang@Atheros.com, netdev@vger.kernel.org, 565404@bugs.debian.org, Xiong.Huang@Atheros.com To: ben@decadent.org.uk Return-path: Received: from ernst.netinsight.se ([194.16.221.21]:25694 "HELO ernst.netinsight.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1760167Ab3DBHpR convert rfc822-to-8bit (ORCPT ); Tue, 2 Apr 2013 03:45:17 -0400 In-Reply-To: <1364689558.3557.22.camel@deadeye.wl.decadent.org.uk> Sender: netdev-owner@vger.kernel.org List-ID: >>>>> "BH" =3D=3D Ben Hutchings writes: BH> On Tue, 2010-01-26 at 09:34 +0100, Anders Bostr=F6m wrote: >> >>>>> "JY" =3D=3D Jie Yang writes: >>=20 JY> Anders Bostr=F6m wrote: >>=20 JY> following is my test cese, >> >>=20 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. >> >>=20 >> >> 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> oops, its my mistake in writing, my case is 1026 device ID >>=20 >> >>=20 JY> Can you give me some advice on how to reproduce this bug?? >> >>=20 >> >> The only suggestion I have is to try to find a board with a >> >> 1026-chip on it. >> >>=20 >> >> 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= =2E >> >>=20 JY> just to check, if the kernel version is 2.6.26-2 ?? >>=20 >> I've tested with >> Debian linux-image-2.6.26-2-amd64 version 2.6.26-19lenny2, >> Debian linux-image-2.6.30-bpo.2-amd64 version 2.6.30-8~bpo50+2 and >> kernel.org 2.6.30.10 amd64 with ethtool patch for setting of tso. S= ame >> result. BH> Does booting with the kernel parameter 'pci=3Dnomsi' avoid the pro= blem? I'm sorry, but I can't test this at the moment. The computer with the TSO-problem is running as a file-server =3D> can't be used for testing. Also, we don't use the Atheros Ethernet interface any more due to other problems, hard hang (need reset) of the Eth-interface every ~6 month's. However, the computer is scheduled to be replaced as file-server quite soon, so I might be able to test this again after the replacement. / Anders