> The IRQ used by ftape gets not freed after usage, so you will get
> "resource busy" on subsequent accesses. I you nevertheless unload
> the module, the kernel will Ooops when doing a 'cat /proc/interrupts'.
> ( id-string pointing to nirvana )
> I suspect also some other drivers not beeing uptodate with the latest
> request_/free_ -irq stuff.
> NOTE: the additional "dev_id" parameter must be equal for request_irq
> and free_irq, else the IRQ will not be freed. The _value_ of the
> pointer is compared, _not_ the contents !
Ugh. I missed that completely.
Thanks for pointing it out and a supplying a patch.
Kai
-- ------------> New email address from 960401: <khp@dolphinics.no> <------------ Kai Harrekilde-Petersen <khp@pip.dknet.dk> Linux: choice of a GNU generation >> Inside every little problem there's a BIG problem, struggling to get out <<