netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: randy_dunlap <rdunlap@xenotime.net>
Cc: herbert@gondor.apana.org.au, netdev@oss.sgi.com, akpm@osdl.org
Subject: Re: 2.6.12-rcx networking oops
Date: Tue, 7 Jun 2005 08:34:51 -0700	[thread overview]
Message-ID: <20050607153451.GA28776@linuxace.com> (raw)
In-Reply-To: <20050606224646.24af30ff.rdunlap@xenotime.net>

On Mon, Jun 06, 2005 at 10:46:46PM -0700, randy_dunlap wrote:
> Agreed, the stack trace is suspicious.  (more below)

Yes, many of the oops i've collected are questionable...

> This is with NAPI, right?  Would it make sense to try it with that
> disabled?  (I don't recall you saying it's NAPI, but the e1000
> functions seem to indicate that.)

It is NAPI, but it works fine up to 2.6.11-rc1.  2.6.11-rc2 fails,
so I'm now testing each individual -bk snapshot between them in 
hopes of finding the offending changeset.  Given that this box
is a firewall, it could be the slew of large netfilter changes
which went into -rc2, but we'll see.

> and how about enabling CONFIG_FRAME_POINTER ?

It is enabled.

Phil

      reply	other threads:[~2005-06-07 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 22:40 2.6.12-rcx networking oops Phil Oester
2005-05-31 23:12 ` Andrew Morton
2005-05-31 23:23   ` Phil Oester
2005-05-31 23:28     ` Andrew Morton
2005-05-31 23:34       ` Phil Oester
2005-06-01  5:49 ` Herbert Xu
2005-06-01 17:00   ` Phil Oester
2005-06-07  5:46     ` randy_dunlap
2005-06-07 15:34       ` Phil Oester [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=20050607153451.GA28776@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=akpm@osdl.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@oss.sgi.com \
    --cc=rdunlap@xenotime.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 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).