From: Paul <lists@loudas.com>
To: "Netfilter (list)" <netfilter@lists.netfilter.org>
Subject: preempt vs SMP
Date: Mon, 11 Apr 2005 12:37:24 +1200 [thread overview]
Message-ID: <4259C6C4.1060200@loudas.com> (raw)
are there any known issues using the preempt patch with smp/netfilter?
I've got a constant error that looks like this:
Apr 10 18:19:07 trinity kernel: BUG: using smp_processor_id() in
preemptible [00000001] code: modprobe/11068
Apr 10 18:19:07 trinity kernel: caller is ip_conntrack_init+0x255/0x369
[ip_conntrack]
Apr 10 18:19:07 trinity kernel: [<c02ec398>] smp_processor_id+0xa8/0xc0
Apr 10 18:19:07 trinity kernel: [<f0cdb275>]
ip_conntrack_init+0x255/0x369 [ip_conntrack]
Apr 10 18:19:07 trinity kernel: [<f0cdb275>]
ip_conntrack_init+0x255/0x369 [ip_conntrack]
Apr 10 18:19:07 trinity kernel: [<f0d45c17>] init_or_cleanup+0x17/0x290
[ip_conntrack]
Apr 10 18:19:07 trinity kernel: [<f0cdb00f>] init+0xf/0x20 [ip_conntrack]
Apr 10 18:19:07 trinity kernel: [<c013d86a>] sys_init_module+0x18a/0x250
Apr 10 18:19:07 trinity kernel: [<c010328f>] syscall_call+0x7/0xb
Apr 10 18:19:07 trinity kernel: BUG: using smp_processor_id() in
preemptible [00000001] code: modprobe/11081
Apr 10 18:19:07 trinity kernel: caller is
ip_conntrack_helper_register+0x18/0x170 [ip_conntrack]
Apr 10 18:19:07 trinity kernel: [<c02ec398>] smp_processor_id+0xa8/0xc0
Apr 10 18:19:07 trinity kernel: [<f0d48848>]
ip_conntrack_helper_register+0x18/0x170 [ip_conntrack]
Apr 10 18:19:07 trinity kernel: [<f0d48848>]
ip_conntrack_helper_register+0x18/0x170 [ip_conntrack]
Apr 10 18:19:07 trinity kernel: [<c02eb2df>] sprintf+0x1f/0x30
Apr 10 18:19:07 trinity kernel: [<f0cdb0d5>] init+0xd5/0x114
[ip_conntrack_ftp]
Apr 10 18:19:07 trinity kernel: [<c013d86a>] sys_init_module+0x18a/0x250
Apr 10 18:19:07 trinity kernel: [<c010328f>] syscall_call+0x7/0xb
reply other threads:[~2005-04-11 0:37 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=4259C6C4.1060200@loudas.com \
--to=lists@loudas.com \
--cc=netfilter@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