I am not sure but I think once oops happens then you may or may not remove the module. I think it really depends on how much the oops has affected the system. Try force remove though but I vaguely recall the same problem and I had to resort to reboot.
On Wed, Nov 5, 2008 at 7:28 AM, <[EMAIL PROTECTED]> wrote: > > > > Hi > > i m facing this prob from long that when i use a module which i have > just inserted. > > now suppose by mistake some kernel oops occur null pointer exception > lets say .. > > now my program which was using the function of module is closed . > > so in my knowledge no one is using my module now. > > > now i corrected the mistake in module re compiled it and tried to > rmmod previous version of module. > > but error came as module is in use cannot rmmod.... > > >i tried to rmmod by force too but its not working ... > > >now to remove earlier module i had to restart PC ...that's a > headache... > > Its not clear, > Are you trying to remove a module, which got kernel-oops ? > > > Regards, > Mythri. > > -- > To unsubscribe from this list: send an email with > "unsubscribe kernelnewbies" to [EMAIL PROTECTED] > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- http://linuxexplained.blogspot.com
