Masters,

I have inserted a linux module which controlls the bandwidth of LAN . Just when I insmod'ed kernel panicked. When restarted I am stunned to find out that many of my other modules are missing. How can insertion of one module removes other modules . I use 2.6.9 kernel on a redhat 3.4.3 version.

The module i inserted did worked well in 2.4 kernel. I tried to insert this same module in to kernel 2.6 expecting to see some error. I never expected that I would loss some modules. I am using kernel threading in the module and i have heard kernel threading for 2.4 and 2.6 are different. But i didnt expect it would eat my modules. Can any one tell me what is the reason behind me losing my modules.
Thanking you .

The insertion of a module, per sé, shouldn't remove any module from memory, let alone the disk.

But, if the kernel crashed, there's a chance that any file that was open at that moment has been corrupted, erased or whatever. That's how crashes work

You should run fsck for all your drives (at least the ones that were mounted when the crash happened).

Mmmm, I wonder how did you compile a module for 2.4 against a 2.6 kernel tree. Or did you just copy the .ko file and tried to run it?

The crash and/or the hard reboot (most probably).

My module worked perfectly well for 2.4 . But when I run the same module on 2.6 some errors where present. Since I am using kernel threads I expected some errors . But none of the errors where based on thread . I made some minor corrections to the module source code like workqueue structure for tq structure. And thus I run make successfully. I havent copied .ko files in to 2.6.

When I insmoded the module some errors like unknown symbols where shown. I changed a expresion in the code and those errors where gone. Then I insmoded kernel panicked and rest you know.

I see. I had to ask. I had not clear if the module was programmed by you or anyone else.

Yep. Then the crash might explain the problem you are experiencing. Overall, if fsck can find errors, in that case the cause of the problem will be almost crystal clear to me. It seems that you will have to do some extra analysis and debugging on your module before you can use it on 2.6.