All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Daniel Blueman <daniel.blueman@gmx.net>
Cc: Antonio Vargas <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 06:39:54 -0400	[thread overview]
Message-ID: <3F8E757A.5010008@pobox.com> (raw)
In-Reply-To: <17122.1066291319@www7.gmx.net>

Daniel Blueman wrote:
> 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?


There is no need to profile, I described the problem precisely.

	Jeff




  reply	other threads:[~2003-10-16 10:40 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
2003-10-16 10:39         ` Jeff Garzik [this message]
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=3F8E757A.5010008@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=daniel.blueman@gmx.net \
    --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 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.