From: Joshua N Pritikin <jpritikin@pobox.com>
To: coreteam@netfilter.org
Cc: netfilter-devel@lists.netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: an oops possibly due to an SMP related bug in netfilter
Date: Mon, 30 Aug 2004 22:55:57 +0530 [thread overview]
Message-ID: <20040830172557.GD1029@always.joy.eth.net> (raw)
In-Reply-To: <20040830165753.GA22979@sch.bme.hu>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On Mon, Aug 30, 2004 at 06:57:53PM +0200, KOVACS Krisztian wrote:
> On Mon, Aug 30, 2004 at 05:38:09PM +0530, Joshua N Pritikin wrote:
> > (Perhaps I am one of the few people crazy enough to run a firewall on
> > an SMP machine. ;-)
> >
> > CPU: 0
> > EIP: 0060:[<c8895955>] Not tainted
> > EFLAGS: 00010246 (2.6.7)
> > EIP is at __ip_conntrack_find+0x179/0x1a0 [ip_conntrack]
> > eax: 00000001 ebx: 00000000 ecx: c0353cc0 edx: 00000000
> > esi: 00000000 edi: 00000000 ebp: c0353c88 esp: c0353c6c
> > ds: 007b es: 007b ss: 0068
> > Process swapper (pid: 0, threadinfo=c0352000 task=c0300980)
>
> I don't think you're the only one running iptables on SMP... This looks
> like a conntrack hash table corruption, so the first thing you should
> check is your memory, of course. Are you 100 percent sure that it is ok?
Fair enough.
Memtest86 doesn't spot anything BUT it could be due to voltage
fluctuation. I guess I can't run this motherboard without a UPS.
--
A new cognitive theory of emotion, http://openheartlogic.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-30 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 12:08 an oops possibly due to an SMP related bug in netfilter Joshua N Pritikin
2004-08-30 16:57 ` KOVACS Krisztian
2004-08-30 17:25 ` Joshua N Pritikin [this message]
2004-08-31 14:56 ` Bill Davidsen
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=20040830172557.GD1029@always.joy.eth.net \
--to=jpritikin@pobox.com \
--cc=coreteam@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.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