kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: sakthi.cdm@gmail.com (sakthi selvam)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Unable to remove kernel module showing permanent using lsmod
Date: Thu, 24 Mar 2011 10:38:08 +0530	[thread overview]
Message-ID: <AANLkTi=0sakZeHHsZufAv3B3d_PUO-aLU+jSEJhH8Ebj@mail.gmail.com> (raw)

Dear All,

Need your assistance:

Currently I am using Wind River Linux distribution OS with kernel
version 2.6.27.39 and Wind River version pne-3. After loading of my
kernel module, I found it was permanent in the kernel using lsmod (for
ex see below Ref 1). When I tried to remove, it was displaying as
?ERROR: Removing 'hsl_module': Device or resource busy?. For your
information, the same module is working fine with the Wind River pne-2
Linux Distribution OS with kernel version 2.6.21.
>From the kernel source, I came to know that only possibility of
showing permanent is ?if there is non-availability of cleanup_module
and with the availability of init_module?.

But in my case, cleanup module also available in memory, after loading
the module. I used to check using the file in /proc/kallsyms for the
availability of cleanup module in memory.

Thanks for reading. Prompt reply is expected to identify the root cause.

Ref 1:
Module                  Size  Used by
hsl_module            530454  0 [permanent]




Thanks,
Sakthi Selvam

             reply	other threads:[~2011-03-24  5:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24  5:08 sakthi selvam [this message]
2011-03-24  6:38 ` Unable to remove kernel module showing permanent using lsmod Mulyadi Santosa
2011-03-24  7:47   ` Kacrut
2011-03-24 15:05     ` Greg KH
2011-03-25  3:21 ` Dave Hylands
2011-04-17  6:19 ` sakthi selvam
2011-04-17 17:14   ` Mulyadi Santosa

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='AANLkTi=0sakZeHHsZufAv3B3d_PUO-aLU+jSEJhH8Ebj@mail.gmail.com' \
    --to=sakthi.cdm@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).