From: Simon Kirby <sim@netnation.com>
To: linux-kernel@vger.kernel.org
Cc: Rusty Russell <rusty@linuxcare.com.au>,
Harald Welte <laforge@gnumonks.org>
Subject: ASSERT: ip_nat_core.c:841 &ip_conntrack_lock not readlocked
Date: Sun, 29 Sep 2002 13:20:34 -0700 [thread overview]
Message-ID: <20020929202034.GA9591@netnation.com> (raw)
2.4.20pre8, up for about a day, stopped responding.
This box is our staff NAT box, and has been stable running 2.4.19-pre4
for 183 days. On Saturday morning, I put 2.4.20-pre8 on, and did not
notice until now that it was spitting these messages everywhere:
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (1014 buckets, 8112 max) - 292 bytes per conntrack
ASSERT ip_conntrack_core.c:624 &ip_conntrack_lock not readlocked
ASSERT ip_conntrack_core.c:94 &ip_conntrack_lock readlocked
ASSERT: ip_nat_core.c:841 &ip_conntrack_lock not readlocked
ASSERT ip_conntrack_core.c:94 &ip_conntrack_lock readlocked
ASSERT ip_conntrack_core.c:1063 &ip_conntrack_lock not readlocked
ASSERT ip_conntrack_core.c:1074 &ip_conntrack_lock not readlocked
ASSERT: ip_nat_core.c:841 &ip_conntrack_lock not readlocked
ASSERT ip_conntrack_core.c:94 &ip_conntrack_lock readlocked
(Taken from after a reboot, but the kern.log is full of these messages
from last time.)
Just now, the box died with the console full of this message:
ASSERT: ip_nat_core.c:841 &ip_conntrack_lock not readlocked
No Oops or backtrace occurred. Sysrq apparently didn't work.
Simon-
[ Simon Kirby ][ Network Operations ]
[ sim@netnation.com ][ NetNation Communications ]
[ Opinions expressed are not necessarily those of my employer. ]
reply other threads:[~2002-09-29 20:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020929202034.GA9591@netnation.com \
--to=sim@netnation.com \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@linuxcare.com.au \
/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.