Message-ID: <40D99A08.90707@ThinRope.net>
Date: Wed, 23 Jun 2004 23:56:08 +0900
From: Kalin KOZHUHAROV <kalin@ThinRope.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040121
MIME-Version: 1.0
To: Mikael Bouillot <xaajimri@corbac.com>
Cc: linux-kernel@vger.kernel.org,
       Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Subject: Re: Forcedeth driver bug
References: <20040623142936.GA10440@mail.nute.net>
In-Reply-To: <20040623142936.GA10440@mail.nute.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2101
Lines: 47

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.

Kalin.

-- 
||///_ o  *****************************
||//'_/>     WWW: http://ThinRope.net/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/