From: Antonio Vargas <wind@cocodriloo.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Antonio Vargas <wind@cocodriloo.com>,
Daniel Blueman <daniel.blueman@gmx.net>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] [2.4.21] 8139too 'too much work at interrupt'...
Date: Wed, 15 Oct 2003 19:20:30 +0200 [thread overview]
Message-ID: <20031015172030.GA20098@wind.cocodriloo.com> (raw)
In-Reply-To: <3F8C3A48.5090703@pobox.com>
On Tue, Oct 14, 2003 at 02:02:48PM -0400, Jeff Garzik wrote:
> Antonio Vargas wrote:
> >This happens to me also on 2.4.18 and 2.4.19 (yes, I know they are old).
> >
> >Happens about once every 5 months, with the box running at
> >about 1 month uptime per reboot (home server, there is no UPS)
>
>
> It's fairly normal for this event to occur. It's due to the 8139
> hardware.. sometimes (perhaps during a DoS or ping flood) you can
> receive far more tiny packets than the driver wishes to deal with in a
> single interrupt.
>
> The real solution is to convert the driver to NAPI...
>
> Jeff
NAPI is the method where you block hardware interrupts and
then handle the data by periodic polling? I wonder how could
I get this error, given that my network is a 10Mbit one ;)
--
winden/network
1. Dado un programa, siempre tiene al menos un fallo.
2. Dadas varias lineas de codigo, siempre se pueden acortar a menos lineas.
3. Por induccion, todos los programas se pueden
reducir a una linea que no funciona.
next prev parent reply other threads:[~2003-10-15 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 10:08 Daniel Blueman
2003-10-09 16:35 ` Antonio Vargas
2003-10-14 18:02 ` Jeff Garzik
2003-10-15 17:20 ` Antonio Vargas [this message]
2003-10-16 8:01 ` Daniel Blueman
2003-10-16 10:39 ` Jeff Garzik
2003-10-16 11:18 ` Daniel Blueman
2003-10-16 11:41 ` Jeff Garzik
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=20031015172030.GA20098@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=daniel.blueman@gmx.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome