From: Lennert Buytenhek <buytenh@gnu.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-mm2] e100 driver hangs after period of moderate receive load
Date: Wed, 31 Dec 2003 07:21:55 -0500 [thread overview]
Message-ID: <20031231122155.GA13323@gnu.org> (raw)
In-Reply-To: <3FF2BCDE.5010302@pobox.com>
On Wed, Dec 31, 2003 at 07:11:10AM -0500, Jeff Garzik wrote:
> >After banging on an e100 card for about ten minutes with a ~60kpps stream,
> >the interface stops receiving packets. Interrupts come in once every few
> >seconds (from /proc/interrupts), but no packets are received anymore at
> >all.
> >Lots of slab corruption messages in the syslog that were generated during
> >that packet stream (see other email I sent.) Stopping the packet stream
> >still leaves the interface unusable. 'ifconfig eth1 down ; ifconfig eth1
> >up'
> >seems to fix things.
>
> Is NAPI enabled for this driver? The interrupt behavior seems normal
> for NAPI, but certainly the rest of the behavior does not...
Yes, NAPI was indeed enabled.
I 'went back' to 2.6.1-rc1 and that seems fine now. Any patches you want
me to try on top of 2.6.0-mm2?
--L
next prev parent reply other threads:[~2003-12-31 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 11:02 [2.6.0-mm2] e100 driver hangs after period of moderate receive load Lennert Buytenhek
2003-12-31 12:11 ` Jeff Garzik
2003-12-31 12:21 ` Lennert Buytenhek [this message]
2003-12-31 12:34 ` Jeff Garzik
2004-01-01 2:21 ` Thomas Molina
2004-01-01 10:27 ` Lennert Buytenhek
2004-01-10 15:49 ` Lennert Buytenhek
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 0:25 Feldman, Scott
[not found] <C6F5CF431189FA4CBAEC9E7DD5441E01034D50AD@orsmsx402.jf.intel.com>
2004-01-10 1:17 ` Feldman, Scott
2004-01-10 15:51 ` Lennert Buytenhek
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=20031231122155.GA13323@gnu.org \
--to=buytenh@gnu.org \
--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;
as well as URLs for NNTP newsgroup(s).