From: Martin Zwickel <martin.zwickel@technotrend.de>
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
Date: Wed, 23 Jun 2004 16:46:27 +0200 [thread overview]
Message-ID: <20040623164627.3234bc29@phoebee> (raw)
In-Reply-To: <20040623142936.GA10440@mail.nute.net>
On Wed, 23 Jun 2004 14:29:36 +0000
Mikael Bouillot <xaajimri@corbac.com> bubbled:
> 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.
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?
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.
Regards,
Martin
--
MyExcuse:
YOU HAVE AN I/O ERROR -> Incompetent Operator error
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
next prev parent reply other threads:[~2004-06-23 14:47 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 [this message]
2004-06-23 16:04 ` Mikael Bouillot
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=20040623164627.3234bc29@phoebee \
--to=martin.zwickel@technotrend.de \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xaajimri@corbac.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox