better way of unloading modules in 2.6.6?

[Igor Gueths]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Kirk. I do in fact have CONFIG_MODULE_UNLOAD=y. However, I wasn't able to determine, in the case of Alsa modules, the order of unloading in 2.6.6. It all seemed to be circular, or at least 
to me it seemed that way. I.E., snd_timer is in use by SND_PCM. Then modprobe -r snd-pcm: Module snd-pcm is in use by snd-emu10k1. Then modprobe -r snd-emu10k1: snd-emu10k1 is in use by 
snd-pcm. And so on. Hmm correct me if I am wrong, however if module unloading is stripped from the kernel, wouldn't that defeat the purpose of modules? I mean I can see reloading the module if 
it crashes, however one wouldn't be able to unload modules they're testing without rebooting? And btw the reason for unloading Alsa modules was because I discovered that after a few days of 
being loaded, and I would try and record something, arecord would mysteriously hang even when supplying it with correct options. I haven't investigated this further, as I am hoping the upgrade 
to Alsa-1.0.5 fixed it. If not, its time to analyze debug output. 
On Thu, Jul 08, 2004 at 06:52:54AM -0400, Kirk Reiser wrote:
> Hi Igor:  In 2.6.x kernels there are two new features in make config
> or menuconfig which ask if you modules to be unloadable.  You might
> want to check those settings because I believe the default is don't
> unload modules.  There is a fairly growing community of kernel hackers
> which because of the problems inherent in unloading modules don't
> think it should be done.
> 
>   Kirk
> 
> -- 
> 
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk at braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
Failure is not an option, it comes bundled with your Microsoft product.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFA7WalNohoaf1zXJMRAj+5AKCC2/IJOMq+hLd2wqzAXTAFK6eEbgCdEtk0
UJ9fcNmbc2FRHpHdD43f9YY=
=Y/o2
-----END PGP SIGNATURE-----