Module XXX can not be unloaded

Module XXX can not be unloaded

[davidsen]

My logs are filled with this message, in spite of:
 1 - nothing is trying to unload these modules
 2 - my kernels are built w/o module unloading because I have never yet 
     found any module which *could* be unloaded by the new code.

I presume this should be replaced by a message saying that module 
unloading is not configured, and that it should only happen when a program 
tries to unload a module, rather than generating many lines of meaningless 
log babble.

-- 
bill davidsen, CTO TMR Associates, Inc <davidsen@tmr.com>
  Having the feature freeze for Linux 2.5 on Hallow'een is appropriate,
since using 2.5 kernels includes a lot of things jumping out of dark
corners to scare you.

Re: Module XXX can not be unloaded

[GertJan Spoelman]

On Sunday 09 March 2003 21:19, davidsen wrote:
> My logs are filled with this message, in spite of:
>  1 - nothing is trying to unload these modules

Are you sure?, some distro's have a default cronjob which do a rmmod -as every 
hour or maybe even more frequent.
The -s logs the message to syslog instead of the terminal.

>  2 - my kernels are built w/o module unloading because I have never yet
>      found any module which *could* be unloaded by the new code.
>
> I presume this should be replaced by a message saying that module
> unloading is not configured, and that it should only happen when a program
> tries to unload a module, rather than generating many lines of meaningless
> log babble.
-- 

    GertJan