Messages in this thread | | | Date | Sun, 9 Mar 2003 15:19:02 -0500 (EST) | From | davidsen <> | Subject | Module XXX can not be unloaded |
| |
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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |