From: Ed Tomlinson <tomlins@cam.org>
To: Helge Hafting <helgehaf@aitel.hist.no>,
"David S. Miller" <davem@redhat.com>
Cc: wli@holomorphy.com, helgehaf@aitel.hist.no,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@digeo.com
Subject: Re: 2.5.69-mm2 Kernel panic, possibly network related
Date: Wed, 7 May 2003 19:24:41 -0400 [thread overview]
Message-ID: <200305071924.41279.tomlins@cam.org> (raw)
In-Reply-To: <20030507215430.GA1109@hh.idb.hist.no>
On May 7, 2003 05:54 pm, Helge Hafting wrote:
> On Wed, May 07, 2003 at 06:40:10AM -0700, David S. Miller wrote:
> > From: William Lee Irwin III <wli@holomorphy.com>
> > Date: Wed, 7 May 2003 07:41:00 -0700
> >
> > In another thread, you mentioned that a certain netfilter cset had
> > issues; I think it might be good to add that as a second possible
> > cause.
> >
> > Good point, Helge what netfilter stuff do you have in use?
> > Are you doing NAT?
>
> I have compiled in almost everything from netfilter, except
> from "Amanda backup protocol support" and "NAT of local connections"
>
> I also have ipv6 compiled, but no ipv6-netfilter.
>
> I don't do any NAT. I used to have some firewall rules, but not currently
> as some previous dev-kernel broke on that. So I have iptables
> with no rules, just an ACCEPT policy for everything. I do no
> routing either, only one network card is used.
I just had mm2 lockup here too. Not sure just what when wrong - my serial
console was not connected. I should be able to try it again later this evening.
I do not use iptables here, I do use ipchains.
Ed Tomlinson
next prev parent reply other threads:[~2003-05-07 23:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 6:23 2.5.69-mm2 Andrew Morton
2003-05-07 10:10 ` 2.5.69-mm2 Kernel panic, possibly network related Helge Hafting
2003-05-07 10:40 ` David S. Miller
2003-05-07 10:49 ` Helge Hafting
2003-05-07 9:56 ` David S. Miller
2003-05-07 14:41 ` William Lee Irwin III
2003-05-07 13:40 ` David S. Miller
2003-05-07 21:54 ` Helge Hafting
2003-05-07 23:24 ` Ed Tomlinson [this message]
2003-05-08 1:38 ` William Lee Irwin III
2003-05-08 6:54 ` Helge Hafting
2003-05-08 7:30 ` Helge Hafting
2003-05-08 8:01 ` William Lee Irwin III
2003-05-08 10:07 ` William Lee Irwin III
2003-05-08 11:04 ` Helge Hafting
2003-05-11 15:06 ` William Lee Irwin III
2003-05-08 11:53 ` Helge Hafting
2003-05-08 12:04 ` Jens Axboe
2003-05-08 13:39 ` Helge Hafting
2003-05-08 13:37 ` Jens Axboe
2003-05-10 7:03 ` William Lee Irwin III
2003-05-10 7:30 ` Jens Axboe
2003-05-08 17:39 ` William Lee Irwin III
2003-05-08 17:21 ` David S. Miller
2003-05-08 21:34 ` Ed Tomlinson
2003-05-08 21:53 ` David S. Miller
2003-05-07 15:20 ` Steven Cole
2003-05-07 15:33 ` William Lee Irwin III
2003-05-09 12:57 ` Bill Davidsen
2003-05-09 17:42 ` Helge Hafting
2003-05-07 12:06 ` William Lee Irwin III
2003-05-09 18:56 J. Hidding
[not found] <fa.f4fihqc.4kq986@ifi.uio.no>
[not found] ` <fa.clherio.l2of82@ifi.uio.no>
2003-05-10 12:18 ` Ed Tomlinson
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=200305071924.41279.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.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).