From: Jes Sorensen <jes@sunsite.dk>
To: Patrick Cole <z@amused.net>
Cc: Dennis Schoen <dennis@cobolt.net>, linux-kernel@vger.kernel.org
Subject: Re: [BUG]: RT8139 Too much work at interrupt, IntrStatus=....
Date: 26 Feb 2002 21:57:05 +0100 [thread overview]
Message-ID: <d3elj8ufku.fsf@lxplus049.cern.ch> (raw)
In-Reply-To: <20020109090855.GA338@cobolt.net> <20020219055243.GA4398@jaded.anu.edu.au>
In-Reply-To: Patrick Cole's message of "Tue, 19 Feb 2002 16:52:43 +1100"
Patrick Cole <z@amused.net> writes:
> Hi dennis, I'm getting these messages too with an identical card...
> 8139 (rev 10)... seems to have started happening after I went to
> 2.4.17... strangely enough I'm getting very similar mæssages on the
> machine right beside it.. running 2.4.13, SMP, and a 3com 3c905b
> (Boomerang).
The problem with the 8139 is the fact that the chip design is really
dumb, when I say dumb here, I mean *really* dumb ;-(
The result is that when the card is bombarded with a lot of small
packets it can livelock because the queues fill up faster than the
kernel code can empty and process them.
I made some changes to improve the situation in the driver, for 2.2
kernels, which I have submitted to Jeff and he plans to integrated
them into the next release.
My patched drivers are available from
http://www.wildopensource.com/proj/download/SG_drivers.html however I
haven't tested them on 2.4.x, so I am not going to bet on them
working.
Cheers,
Jes
prev parent reply other threads:[~2002-02-26 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 9:08 [BUG]: RT8139 Too much work at interrupt, IntrStatus= Dennis Schoen
[not found] ` <Pine.LNX.4.33.0201091759120.22941-100000@coffee.psychology.mcmaster.ca>
2002-01-10 9:52 ` Dennis Schoen
2002-02-19 5:52 ` Patrick Cole
2002-02-26 20:57 ` Jes Sorensen [this message]
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=d3elj8ufku.fsf@lxplus049.cern.ch \
--to=jes@sunsite.dk \
--cc=dennis@cobolt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=z@amused.net \
/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.