From: Roger Crandell <rwc@lanl.gov>
To: linux-kernel@vger.kernel.org
Subject: multiprocessor kernel problem
Date: Fri, 01 Dec 2000 09:41:58 -0700 [thread overview]
Message-ID: <3A27D4D6.4DA47346@lanl.gov> (raw)
I have 2.4.0 test 10 and test 11 installed on a multiprocessor (Intel)
machine. I have tried both test versions of the kernel. I configured
the kernel for single
and multi processor. When I boot single processor, iptables will run
fine. When I boot the machine with the multiprocessor kernel and run
iptables, the kernel dumps several pages of hex and the final two lines
of output are:
Killing interrupt handler
scheduling in interrupt
The kernel logs nothing and you must reset the machine to bring it back
up. I believe this is a kernel issue rather than an iptables
issue.
Does anyone have experience with iptables on a multiprocessor machine?
I am not currently subscribed to this list, so may I please be
personally CC'ed with the
answers/comments posted to the list? I have also submitted this to the
netfilter list of which I am
a member.
Roger Crandell
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-01 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 16:41 Roger Crandell [this message]
2000-12-01 22:48 ` multiprocessor kernel problem Peter Samuelson
2000-12-01 23:01 ` Keith Owens
2000-12-02 16:12 ` Johan Kullstam
2000-12-03 2:08 ` Rusty Russell
2000-12-04 0:22 ` Johan Kullstam
2000-12-04 5:21 ` Rusty Russell
2000-12-04 20:56 ` Roger Crandell
2000-12-04 23:53 ` Johan Kullstam
2000-12-04 1:30 ` Roger Crandell
-- strict thread matches above, loose matches on Subject: below --
2000-12-01 16:57 Roger Crandell
2000-12-02 16:15 ` Johan Kullstam
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=3A27D4D6.4DA47346@lanl.gov \
--to=rwc@lanl.gov \
--cc=linux-kernel@vger.kernel.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