Re: [BUG] [2.4.21] 8139too 'too much work at interrupt'...

From: Daniel Blueman
Date: Thu Oct 16 2003 - 03:03:34 EST


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! +++

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/