From: Pablo Neira <pablo@eurodev.net>
To: Sumit Pandya <sumit@elitecore.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: OOPS: Kernel-2.4.26
Date: Mon, 03 Jan 2005 18:49:12 +0100 [thread overview]
Message-ID: <41D98598.8010602@eurodev.net> (raw)
In-Reply-To: <HGEFKOBCHAIJDIEJLAKDMEONCAAA.sumit@elitecore.com>
Sumit Pandya wrote:
>>ip_conntrack_h323 2688 1
>>ip_conntrack_talk 2624 2
>>ip_conntrack_tftp 2272 1
>>ip_conntrack_pptp 3136 1
>>ip_conntrack_proto_gre 2240 0 [ip_nat_pptp ip_conntrack_pptp]
>>ip_conntrack_irc 4032 1
>>ip_conntrack_ftp 4544 1
>>
>>
Hm, you are using some conntrack/nat helpers which are marked as testing
in the SVN repository. You've also pointed out that you've applied the
patch to fix the problem of orphaned expectations.
>><[ip_conntrack]ip_conntrack_remove_expectations+30/80> <=====
>>
>>
AFAIK nobody running a standalone kernel has complaint about a bug
related to expectations in last days.
I think that perhaps this could be a hard to trigger bug in one of those
helpers. So the first step is knowing which one is triggering the oops,
but it's hard to know if you run all together. To find out which one is
the problematic, I would do the following:
a) run the system for some time with non-patched kernel, just to make
sure that this is not a bug in the stable kernel branch.
b) run just one of the testing modules at a time.
And try to figure out what's triggering the oops.
Then you could give us more useful information to fix the problem. If
someone else have a better method to hunt the bug, please let me know :)
--
Pablo
prev parent reply other threads:[~2005-01-03 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 12:00 OOPS: Kernel-2.4.26 Sumit Pandya
2005-01-03 14:55 ` Sumit Pandya
2005-01-03 17:49 ` Pablo Neira [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=41D98598.8010602@eurodev.net \
--to=pablo@eurodev.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=sumit@elitecore.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 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.