netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com, herbert@gondor.apana.org.au
Subject: Re: 2.6.12-rcx networking oops
Date: Tue, 31 May 2005 16:23:26 -0700	[thread overview]
Message-ID: <20050531232326.GA17289@linuxace.com> (raw)
In-Reply-To: <20050531161220.4af50a69.akpm@osdl.org>

On Tue, May 31, 2005 at 04:12:20PM -0700, Andrew Morton wrote:
> Are you _sure_ the hardware is good?

Well, it lasts on 2.6.10 indefinitely (since 1/1/5 minus the recent
upgrade attempts).  And the hardware itself has been in service for
a few years without failure.  It will last on 2.6.11 or 12-rc over
the weekend fine, but as soon as traffic picks up during the workday
it keels over.

> Are you running anything which would cause netdevs to be destroyed? 
> Bringing virtual devices up and down?  TUN/TAP driver?  Bonding driver? 
> Anything like that?

The box runs keepalived (for VRRP), and quagga (for OSPF).  Neither should
be destroying netdevs during normal operation AFAIK.

> Have you tried CONFIG_DEBUG_SLAB and/or CONFIG_DEBUG_PAGEALLOC?

No - do you think it would reveal anything given the above?

Phil

  reply	other threads:[~2005-05-31 23:23 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 [this message]
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

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=20050531232326.GA17289@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=akpm@osdl.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@oss.sgi.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).