mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Molina <tmolina@cablespeed.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Lennert Buytenhek <buytenh@gnu.org>, 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 21:21:56 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0312312115120.3069@localhost.localdomain> (raw)
In-Reply-To: <3FF2C266.8010104@pobox.com>



On Wed, 31 Dec 2003, Jeff Garzik wrote:

> Lennert Buytenhek wrote:
> > 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?
> 
> 
> Well, the two are vastly different, since -mm2 includes a complete 
> rewrite of e100.
> 
> Does disabling NAPI in -mm2 change anything?

I have one of these beasts so I decided to test it after seeing this 
message.  2.6.0-mm2 NAPI enabled and I am not seeing any of the symptoms 
described here.  My test consists of downloading an iso from RedHat's ftp 
site.  I'm not sure that is generating the kind of traffic you are talking 
about, but I'm open to suggestions on what test to run trying to duplicate 
what is being reported.

  reply	other threads:[~2004-01-01  2:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 11:02 Lennert Buytenhek
2003-12-31 12:11 ` Jeff Garzik
2003-12-31 12:21   ` Lennert Buytenhek
2003-12-31 12:34     ` Jeff Garzik
2004-01-01  2:21       ` Thomas Molina [this message]
2004-01-01 10:27         ` Lennert Buytenhek
2004-01-10 15:49       ` Lennert Buytenhek
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=Pine.LNX.4.58.0312312115120.3069@localhost.localdomain \
    --to=tmolina@cablespeed.com \
    --cc=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

all inboxes | Powered by JetHome®