[lkml]   [2003]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectModule 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 <>
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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.020 / U:15.324 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site