lkml.org 
[lkml]   [2005]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Trouble unloading a module..
James Hansen wrote:
> 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..

--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-11-01 04:59    [W:0.033 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site