From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268552AbUGXMiJ (ORCPT ); Sat, 24 Jul 2004 08:38:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268553AbUGXMiJ (ORCPT ); Sat, 24 Jul 2004 08:38:09 -0400 Received: from pop.gmx.net ([213.165.64.20]:62083 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S268552AbUGXMiE (ORCPT ); Sat, 24 Jul 2004 08:38:04 -0400 X-Authenticated: #21910825 Message-ID: <41025826.1010006@gmx.net> Date: Sat, 24 Jul 2004 14:37:58 +0200 From: Carl-Daniel Hailfinger User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6) Gecko/20040114 X-Accept-Language: de, en MIME-Version: 1.0 To: Kalin KOZHUHAROV CC: Mikael Bouillot , linux-kernel@vger.kernel.org Subject: Re: Forcedeth driver bug References: <20040623142936.GA10440@mail.nute.net> <40D99A08.90707@ThinRope.net> In-Reply-To: <40D99A08.90707@ThinRope.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Kalin KOZHUHAROV schrieb: > Mikael Bouillot wrote: > >> Hi all, >> >> I'm having trouble with the forcedeth driver in kernel version 2.6.7. >> >>> From what I can see, it seems that incoming packets sometime get stuck >> >> on their way in. >> >> What happens is this: some packet enters the NIC, and for some reason, >> it doesn't come out of the driver. As soon as another incoming packet >> gets in, both packets are handed down by the driver. >> >> It is usually invisible during normal TCP operation, as there are >> several packets in flight and the stuck packet gets pushed down by the >> one following it very soon. But for lockstep protocols like SMB, it very >> annoying as it means you get "blanks" of 2 to 5 seconds during the >> transfer. >> >> I can reproduce this very easily with a modified version of ping. I >> do a flood ping from another machine to the one with the nvnet NIC, but >> I modified ping to send a new packet if one gets "lost" only 10 seconds >> later instead of after 10 ms. The result is that after a couple hundred >> ping-pong at full speed, one ping gets stuck. After 10 seconds, another >> ping is sent and both pong come back. >> >> This didn't happen with the proprietary nvnet driver on kernel 2.4.24. >> My hardware is a nForce 2 mobo (in a shuttle SN45G barebones). >> >> Is this a know bug? If someone working on it already or should I >> investigate the matter further? Please CC any reply to me as I'm not on >> the list. > > > Search http://groups.google.com/ or somewhere else in LKML for "new > device support for forcedeth.c" > > Try the latest patch ( forcedeth_gigabit_try17.txt was the one I tested > last) and report back. > The driver has undergone quite a lot of patching lately. > AFAIR, while testing it, similar effect was observed, but the it was way > broken anyway. Could you please try Linux 2.6.8-rc2 without any driver patch? It has the latest version of forcedeth and I am very interested in any bug reports/ side effects of the update. Regards, Carl-Daniel -- http://www.hailfinger.org/