On Sat, 2002-01-12 at 10:38, Mark Bigler wrote: > Occasionally removing a loaded kernel module can cause problems (this > could happen w/o your doing anything if the module was loaded/unloaded > via the hotplug tools). Some modules hook themselves into kernel > services, and, if a subsequent module uses the same hooks, you have a > potential for disaster when one is removed. Or a background userland > program may be using a module interface, if the module is removed > unexpectedly, the user program, calling into the non-existant module, > can crash the kernel. The latter usually requires you, as root, to > make some change to the system. The former can happen with poorly > configured kernels, as an example, just by unplugging a USB printer > that is currently printing a job.
i'll look into it, considering this is redhat's kernel and it just hooks up modules as needed. that's actually an excellent avenue to explore. most of the time i compile every module i use into the kernel proper. this is because modprobe rarely works for me. not like anything else ever does... now that i think about it, it _might_ be esound... > Most kernel crashes are due to bad device drivers. The NVIDIA binary > only drivers have been an ongoing source of strange crashes. gave my GeForce2 to my younger sister for a christmas present (she consequently got _less_ of the soapmaking stuff...) i'm running a radeon right now.
