All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Matt Brown <matt@mattb.net.nz>
Cc: marcelo.tosatti@cyclades.com, kernel@linuxace.com,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	dlstevens@us.ibm.com, davem@redhat.com
Subject: Re: Kernel panic in 2.4.25
Date: Sun, 04 Apr 2004 19:02:17 -0700	[thread overview]
Message-ID: <4070BE29.9050305@us.ibm.com> (raw)
In-Reply-To: <1081129354.1611.44.camel@argon.shr.crc.net.nz>

Matt Brown wrote:

> Was any progress made on this problem?
> 
> I am seeing the same panic as was originally reported using both kernel
> 2.4.25 and 2.4.26-rc1, I can easily reproduce it under the same
> conditions as Hasso described in the original email. 
> 
> With quagga/ospfd running I simply execute
> ifconfig eth0 down
> ifconfig eth0 up 
> in quick succession and a panic follows within 20 seconds. 
> 
> The panic does not occur if ospfd is not running, or if i pause for at
> least 10 seconds between the two commands. 
> 
> Let me know if I can provide any more information that would be helpful
> in solving this problem. 

Could you try applying the following patch:

http://marc.theaimsgroup.com/?l=linux-netdev&m=108079992001559&w=2

thanks,
Nivedita





  reply	other threads:[~2004-04-05  2:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05  1:42 Kernel panic in 2.4.25 Matt Brown
2004-04-05  2:02 ` Nivedita Singhvi [this message]
2004-04-05  2:45   ` Matt Brown
2004-04-05  2:53     ` Nivedita Singhvi
2004-04-05 14:22 ` Marcelo Tosatti
2004-04-06  9:00   ` Hasso Tepper
2004-04-06  9:28     ` Matt Brown
  -- strict thread matches above, loose matches on Subject: below --
2004-03-25 22:35 Hasso Tepper
2004-03-28 16:11 ` Hasso Tepper
2004-03-28 16:32   ` Phil Oester
2004-03-28 16:49     ` Phil Oester
2004-03-28 17:33       ` Hasso Tepper
2004-03-28 18:25         ` Phil Oester
2004-03-28 19:17           ` Hasso Tepper
2004-03-29 18:54             ` Marcelo Tosatti

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=4070BE29.9050305@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=davem@redhat.com \
    --cc=dlstevens@us.ibm.com \
    --cc=kernel@linuxace.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=matt@mattb.net.nz \
    /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.