From: glynis@butterfly.hjsoft.com
To: mk@fashaf.co.za
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18 Kernel Panics related to Netfilter/iptables
Date: Tue, 3 Sep 2002 00:15:30 -0400 [thread overview]
Message-ID: <20020903041530.GB13142@butterfly.hjsoft.com> (raw)
In-Reply-To: <20020902082156.GA28503@fashaf.co.za>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
On Mon, Sep 02, 2002 at 10:21:56AM +0200, mk@fashaf.co.za wrote:
> One of my machines running kernel 2.4.18 is getting kernel panics
intermittently (30minutes to 4/5 hours).
> from the logs I believe is the culprit:
> kernel: LIST_DELETE: ip_conntrack_core.c:165
`&ct->tuplehash[IP_CT_DIR_REPLY]'(c6c78e44) not in &ip_conntrack_hash
[hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
i've wrestled quite a bit with this problem, but never really could
figure out the correct answers. some people blamed the compiler, but
different versions of the compiler still produced it.
i saw it in 2.4.18 and 2.4.19pre kernels on my dual athlon.
in the end i found switching from snat to masqerading for my internal
network seemed to eliminate it. also i found that if i eliminated my
udp outgoing remote log stream from syslog-ng, i could keep the snat
and have the box still live.
i'm now running nicely with 2.4.19, snat firewall rules, and no remote
logging.
--
____________________}John Flinchbaugh{______________________
| glynis@hjsoft.com http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-09-03 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 8:21 mk
2002-09-03 2:55 ` Rusty Russell
2002-09-03 9:05 ` mk
2002-09-03 4:15 ` glynis [this message]
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=20020903041530.GB13142@butterfly.hjsoft.com \
--to=glynis@butterfly.hjsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mk@fashaf.co.za \
/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
all inboxes | Powered by JetHome®