Trouble unloading a module..
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 1 line · James Hansen
However, on a 64bit machine (unofficial amd/emt64 debian with 2.6.8), even though it seems to unload corrrectly, I get a kernel oops if an application that uses the driver attempts to connect to the device after it's been unloaded.
I'm guessing the driver isn't properly unregistering itself from wherever it is it has registered with (block/character device). Anything where the driver is registering function pointers, references, etc. to itself needs to be cleaned up on module removal.
The oops stacktrace may point to what it is that has been left behind..
Signature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/