From: Phil Oester <kernel@linuxace.com>
To: Hasso Tepper <hasso@estpak.ee>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic in 2.4.25
Date: Sun, 28 Mar 2004 08:49:36 -0800 [thread overview]
Message-ID: <20040328164936.GA21839@linuxace.com> (raw)
In-Reply-To: <20040328163210.GA21803@linuxace.com>
If you are using E100's, can you backout (patch -R) this patch from
2.4.25 vanilla:
http://linux.bkbits.net:8080/linux-2.4/gnupatch@401f2442_DogKaCRsaoMURrjvGCz4w
if using E1000's, can you backout this patch:
http://linux.bkbits.net:8080/linux-2.4/gnupatch@402212c1G2hqO92c1xCHTWJ4AFBFPQ
And see if this stops the panics?
Phil Oester
> On Sun, Mar 28, 2004 at 07:11:06PM +0300, Hasso Tepper wrote:
> > Hasso Tepper wrote:
> > > It's almost 100% (sometimes it just hangs) reproducable for me
> > > although in somewhat strange situation. I have to run Quagga/Zebra
> > > routing suite with zebra and ospfd daemons running. Networking
> > > restart script (removing 60 vlans, creating them again and
> > > assigning IPs to them) leads to panic. Process isn't always
> > > swapper, I have seen ip and kupdated as well, but trace is always
> > > same. I can't reproduce it with 2.4.20 kernel.
> >
> > It's introduced with 2.4.25-rc1 (2.4.25-pre8 is OK). And it's still
> > there in 2.4.26-rc1.
next prev parent reply other threads:[~2004-03-28 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 22:35 Kernel panic in 2.4.25 Hasso Tepper
2004-03-28 16:11 ` Hasso Tepper
2004-03-28 16:32 ` Phil Oester
2004-03-28 16:49 ` Phil Oester [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 1:42 Matt Brown
2004-04-05 2:02 ` Nivedita Singhvi
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
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=20040328164936.GA21839@linuxace.com \
--to=kernel@linuxace.com \
--cc=hasso@estpak.ee \
--cc=linux-kernel@vger.kernel.org \
/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