public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Blueman" <daniel.blueman@gmx.net>
To: Antonio Vargas <wind@cocodriloo.com>
Cc: jgarzik@pobox.com, wind@cocodriloo.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] [2.4.21] 8139too 'too much work at interrupt'...
Date: Thu, 16 Oct 2003 10:01:59 +0200 (MEST)	[thread overview]
Message-ID: <17122.1066291319@www7.gmx.net> (raw)
In-Reply-To: 20031015172030.GA20098@wind.cocodriloo.com

I have seen problems like this when a bad driver was spending loads of time
in it's SA_INTERRUPT (ie meant to be 'fast') IRQ handler ...this buffered up
*lots * of packets to be handled, and caused this message.

Perhaps we should profile?

Dan

> 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.
> 

-- 
Daniel J Blueman

NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService

Jetzt kostenlos anmelden unter http://www.gmx.net

+++ GMX - die erste Adresse für Mail, Message, More! +++


  reply	other threads:[~2003-10-16  8:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 10:08 [BUG] [2.4.21] 8139too 'too much work at interrupt' Daniel Blueman
2003-10-09 16:35 ` Antonio Vargas
2003-10-14 18:02   ` Jeff Garzik
2003-10-15 17:20     ` Antonio Vargas
2003-10-16  8:01       ` Daniel Blueman [this message]
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=17122.1066291319@www7.gmx.net \
    --to=daniel.blueman@gmx.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wind@cocodriloo.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