From: Mikael Bouillot <xaajimri@corbac.com>
To: linux-kernel@vger.kernel.org
Cc: Martin Zwickel <martin.zwickel@technotrend.de>
Subject: Re: Forcedeth driver bug
Date: Wed, 23 Jun 2004 16:04:03 +0000 [thread overview]
Message-ID: <20040623160403.GA11348@mail.nute.net> (raw)
In-Reply-To: <20040623164627.3234bc29@phoebee>
> Do you really know that the driver don't get the stuck packet. Or is it possible
> that the kernels network stack does the fault?
No, I'm not sure it's the driver's fault. I have this problem since I
switched from nvnet to forcedeth and from 2.4.24 to 2.6.7. But I suspect
this is the drivers fault because:
* I have tried to reproduce it on another 2.6.7 machine (with a
different driver) and failed.
* Such an important bug in the network stack would hardly go unnoticed.
* The forcedeth driver is still new and somewhat untested :-)
> I'm asking because I have a similar problem with udp and kernel 2.6.7-rc2-mm2.
> My sendto gets stuck sometimes and only continues if the kernel handles another
> network packet.
>
> But maybe my problem is a totally different one.
In my case, it's the incoming packets that get stuck. Outgoing packets
work just fine. But then again, I'm not sure without running further
tests. I sent my message to the list mainly to know if this was a well
know bug.
--
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
next prev parent reply other threads:[~2004-06-23 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 14:29 Forcedeth driver bug Mikael Bouillot
2004-06-23 14:46 ` Martin Zwickel
2004-06-23 16:04 ` Mikael Bouillot [this message]
2004-06-23 14:56 ` Kalin KOZHUHAROV
2004-06-23 15:57 ` Carl-Daniel Hailfinger
2004-06-23 16:14 ` Mikael Bouillot
2004-06-23 17:02 ` Mikael Bouillot
2004-07-24 12:37 ` Carl-Daniel Hailfinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040623160403.GA11348@mail.nute.net \
--to=xaajimri@corbac.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.zwickel@technotrend.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.