From: Georgi Alexandrov <georgi.alexandrov@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: removing iptable_nat module problem.
Date: Fri, 17 Mar 2006 19:17:57 +0200 [thread overview]
Message-ID: <441AEF45.6080200@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
Hello,
I've tried to modprobe -r iptable_nat on a debian testing system running
debian's 2.6.15-1-686 kernel. Now modprobe is taking 99% cpu resources
and can't be killed even with -9. I've tried to kill it's parents (ssh
---- bash --- modprobe) but that didn't help too.
I don't want to restart the machine as it is a production one and alot
of people count on it.
Exactly the same thing happened when the machine was in the "testlab"
(pre deployment) and i tried to rmmod ip_conntrack.
Is that some kind of kernel issue? Can i stop that process someway?
thanks in advance
--
regards,
Georgi Alexandrov
Key Server = http://pgp.mit.edu/ :: KeyID = 37B4B3EE
Key Fingerprint = E429 BF93 FA67 44E9 B7D4 F89E F990 01C1 37B4 B3EE
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
reply other threads:[~2006-03-17 17:18 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=441AEF45.6080200@gmail.com \
--to=georgi.alexandrov@gmail.com \
--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