All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Fuchs <richard.fuchs@inode.info>
To: Scott Feldman <sfeldma@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: slab corruption in skb allocs
Date: Sat, 05 Mar 2005 20:10:22 +0100	[thread overview]
Message-ID: <422A041E.40105@inode.info> (raw)
In-Reply-To: <93832c6db45c33f7b2f195aae0d469dc@pobox.com>

Scott Feldman wrote:

> Was NAPI turned on for e100 in 2.6.7?  If not, turn NAPI on in the 2.6.7 
> driver and see if you get the same result.  If you do, it's very likely 
> the bug is in the e100 driver's NAPI implementation.

looks like you are right, enabling NAPI in 2.6.7 does trigger this.

what exactly is this? i didn't enable NAPI in any of the newer kernel 
versions i was trying, so i'm somewhat confused. :)  also, does this 
affect the e1000 driver in any way?

cheers
richard

  reply	other threads:[~2005-03-05 20:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04  9:55 slab corruption in skb allocs Richard Fuchs
2005-03-04 11:53 ` Andrew Morton
2005-03-04 12:23   ` Richard Fuchs
2005-03-04 20:11     ` Matt Mackall
2005-03-04 21:19       ` Richard Fuchs
2005-03-04 21:27         ` Matt Mackall
2005-03-04 21:52           ` Richard Fuchs
2005-03-04 22:05             ` Matt Mackall
2005-03-04 22:51               ` Richard Fuchs
2005-03-05 18:25     ` Scott Feldman
2005-03-05 19:10       ` Richard Fuchs [this message]
2005-03-06 17:44         ` Scott Feldman
2005-03-06 18:40           ` Richard Fuchs
2005-03-07  5:07             ` Scott Feldman
2005-03-07  8:30               ` Richard Fuchs
2005-03-04 18:10 ` Dave Jones
2005-03-04 18:32   ` Richard Fuchs
2005-03-04 19:29     ` Richard Fuchs
2005-03-21 22:36 ` Andrew Morton

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=422A041E.40105@inode.info \
    --to=richard.fuchs@inode.info \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfeldma@pobox.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.