netdev
[Top] [All Lists]

Re: 2.6.12-rcx networking oops

To: Phil Oester <kernel@xxxxxxxxxxxx>
Subject: Re: 2.6.12-rcx networking oops
From: Andrew Morton <akpm@xxxxxxxx>
Date: Tue, 31 May 2005 16:28:37 -0700
Cc: netdev@xxxxxxxxxxx, herbert@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050531232326.GA17289@xxxxxxxxxxxx>
References: <20050531224012.GA16789@xxxxxxxxxxxx> <20050531161220.4af50a69.akpm@xxxxxxxx> <20050531232326.GA17289@xxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
Phil Oester <kernel@xxxxxxxxxxxx> wrote:
>
> 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.

hm, OK.  So I assume the machine has recently been running 2.6.10.  So it's
unlikely to be a hardware problem.

> > 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.

OK.  It would need more than a very-ex-net person to work out how those
things affect the networking stack ;)

> > Have you tried CONFIG_DEBUG_SLAB and/or CONFIG_DEBUG_PAGEALLOC?
> 
> No - do you think it would reveal anything given the above?

It might catch the failure at an earlier stage.

<Prev in Thread] Current Thread [Next in Thread>