Re: Trouble unloading a module..

[James Hansen <linux-kernel-list@f0rmula.com>]

Update:

Just tried the driver with a 2.6.14 and it doesn't suffer the same 
problem.  As it looks to be doing what is required to unregister the 
chrdev, I'm loath to suggest it, but could this be a bug in the 2.6.8 
kernel?

Just a thought, so please shoot me down if I'm completly wrong :)

Cheers,

James


Arjan van de Ven wrote:

>On Wed, 2005-11-02 at 12:13 +0000, James Hansen wrote:
>  
>
>>I was thinking that there may have been a common issue that would allow 
>>a driver oops the kernel if not unloaded properly.  Obviously not.
>>
>>Thanks for any advice, it's much appreciated.
>>    
>>
>
>static struct pci_device_id nfp_pci_tbl[] __devinitdata = {
>
>you probably don't want that __devinitdata there....
>
>
>
>
>.
>
>  
>