From: Ron Arts <raarts@netland.nl>
To: netfilter-devel@lists.netfilter.org
Subject: ASSERT ip_conntrack_core.c:622 &ip_conntrack_lock not readlocked
Date: Wed, 12 Mar 2003 21:34:13 +0100 [thread overview]
Message-ID: <3E6F99C5.1050101@netland.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
I get this error on kernel 2.4.21pre4 when I boot. RH 2.4.18 didn't have this problem:
Mar 12 14:05:52 n000007 kernel: ASSERT ip_conntrack_core.c:622 &ip_conntrack_lock not readlocked
Mar 12 14:05:52 n000007 last message repeated 2 times
Mar 12 14:05:52 n000007 kernel: unable to load module ip_conntrack_ftp
Mar 12 14:05:52 n000007 kernel: ip_nat_ftp: error registering helper for port 121
Mar 12 14:05:52 n000007 kernel: ASSERT ip_conntrack_core.c:622 &ip_conntrack_lock not readlocked
Mar 12 14:05:52 n000007 nbs-iptables: /lib/modules/2.4.21-0NBS/kernel/net/ipv4/netfilter/ip_nat_ftp.o:
Mar 12 14:05:52 n000007 nbs-iptables: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO
or IRQ parameters
Mar 12 14:05:52 n000007 nbs-iptables: init_module: Device or resource busy
Mar 12 14:05:52 n000007 nbs-iptables: /lib/modules/2.4.21-0NBS/kernel/net/ipv4/netfilter/ip_nat_ftp.o: insmod /lib/modules/2
.4.21-0NBS/kernel/net/ipv4/netfilter/ip_nat_ftp.o failed
Mar 12 14:05:52 n000007 nbs-iptables: /lib/modules/2.4.21-0NBS/kernel/net/ipv4/netfilter/ip_nat_ftp.o: insmod ip_nat_ftp fai
led
Is this a known problem?
Ron Arts
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3465 bytes --]
next reply other threads:[~2003-03-12 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 20:34 Ron Arts [this message]
2003-03-12 22:45 ` ASSERT ip_conntrack_core.c:622 &ip_conntrack_lock not readlocked Martin Josefsson
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 13:09 Ron Arts
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=3E6F99C5.1050101@netland.nl \
--to=raarts@netland.nl \
--cc=netfilter-devel@lists.netfilter.org \
--cc=raarts@office.netland.nl \
/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.