From: Lennert Buytenhek <buytenh@gnu.org>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-mm2] e100 driver hangs after period of moderate receive load
Date: Sat, 10 Jan 2004 10:51:50 -0500 [thread overview]
Message-ID: <20040110155150.GC23063@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0401091715010.3118-100000@localhost.localdomain>
On Fri, Jan 09, 2004 at 05:17:40PM -0800, Feldman, Scott wrote:
> > > 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?
>
> Lennert, would you mind trying this patch to verify that problem is fixed?
>
> The driver was indicating skbs to the stack before h/w was done with the
> DMA. Not good. That's what causes the corruption. The stack free's the
> skb, and then h/w writes to it's data area.
AFAICS, didn't help, I still get the slab corruption. Anything else you
want me to try? Do you want me to send the klogd output I get now?
--L
next prev parent reply other threads:[~2004-01-10 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C6F5CF431189FA4CBAEC9E7DD5441E01034D50AD@orsmsx402.jf.intel.com>
2004-01-10 1:17 ` [2.6.0-mm2] e100 driver hangs after period of moderate receive load Feldman, Scott
2004-01-10 15:51 ` Lennert Buytenhek [this message]
2004-01-05 0:25 Feldman, Scott
-- strict thread matches above, loose matches on Subject: below --
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
2004-01-01 10:27 ` Lennert Buytenhek
2004-01-10 15:49 ` 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=20040110155150.GC23063@gnu.org \
--to=buytenh@gnu.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.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 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).