On Thu, Mar 24, 2011 at 02:47:15PM +0700, Kacrut wrote: > On 03/24/2011 01:38 PM, Mulyadi Santosa wrote: > > On Thu, Mar 24, 2011 at 12:08, sakthi selvam<sakthi.cdm@xxxxxxxxx> wrote: > >> 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. > > AFAIK, such thing could happen due to certain data structure(s) from > > that module that are continously accessed or locked. So, to avoid race > > condition ( and missing pointer), keeping the module in memory is the > > right way to do. > > > > But of course, AFAIK too, you can try rmmod -f. But the risk is all yours. > > > I got same problem too. Doing rmmod -f doesnt solve it. Any other solution? Nope, your kernel is probably configured to not allow kernel modules to be unloaded. I would ask your vendor about this as they are the ones that can support your kernel the best, not the community. best of luck, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
