From: Phil Oester <kernel@linuxace.com>
To: Hasso Tepper <hasso@estpak.ee>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
dlstevens@ibm.com, linux-net@vger.kernel.org
Subject: Re: Kernel panic in 2.4.25
Date: Sun, 28 Mar 2004 10:25:22 -0800 [thread overview]
Message-ID: <20040328182522.GA22382@linuxace.com> (raw)
In-Reply-To: <200403282033.16204.hasso@estpak.ee>
Do you have CONFIG_IP_MULTICAST enabled in your .config? I don't, and
a couple of the changes in this changeset depend upon it.
I also run ospfd, so maybe you've hit upon something here...cc'ing
linux-net for comment
Phil
p.s. here's a bookmarkable link to that changeset:
http://linux.bkbits.net:8080/linux-2.4/cset@401ee07fZyaInErbsMYxlCIQSlevFQ?nav=index.html|ChangeSet@-9M
On Sun, Mar 28, 2004 at 08:33:16PM +0300, Hasso Tepper wrote:
> Now when linux.bkbits.net is working again, I walked through patches
> between 2.4.25-pre8 and 2.4.25-rc1 and reverted this patch -
> http://linux.bkbits.net:8080/linux-2.4/cset%
> 401.1290.17.1?nav=index.html|ChangeSet@-9M
>
> This solved problem for me, seems (tested only with 2.4.25-rc1 for
> now). I had feeling that it's related to multicast from the beginning
> because I couldn't reproduce panic when I hadn't ospfd daemon running
> (ospf uses multicast).
next prev parent reply other threads:[~2004-03-28 18:25 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
2004-03-28 17:33 ` Hasso Tepper
2004-03-28 18:25 ` Phil Oester [this message]
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=20040328182522.GA22382@linuxace.com \
--to=kernel@linuxace.com \
--cc=dlstevens@ibm.com \
--cc=hasso@estpak.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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