On one of the computers I'm running my driver on, I try to replace a module
that was previously placed in /lib/modules/linux-2.4.17/kernel/driver/usb/.
Upon doing so, at least that's how it seems, I get strange errors. I can
insert my new module and it loads and registers with usb core fine. But then,
if there is a disconnect and then a reconnect, I start getting these errors
from dmesg:
usb.c: failed to register rasid driver
Rasid Driver failed to register
These occur after every disconnect and reconnect. Sometimes multiple times
for each disconnect and reconnect.
The second printk is from my driver.
Even more strange, if I rmmod my new driver, change the source code
so that it does not contain the printk("Rasid Driver failed to register"),
that line still gets printed.
I've grepped the usb source and I cannot find any printk like my line,
and I know the first message is on failure to register. I only call
usb_register() from init_module. How can this occur? Are the mod utils with
2.4.17 buggy?
Anton
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
