orinoco_cs module removal problem
I just switched from 2.5.68 to 2.5.70, and I'm having trouble removing the orinoco_cs module on the fly. After bringing the interface down, doing an "rmmod orinoco_cs" causes the rmmod process to lock up, and subseqeunt invocations of lsmod and 'cat /proc/modules' to do the same. I get a bunch of messages like the following in the kernel log:
"unregister_netdevice: waiting for eth2 to become free. Usage count = 1
However, eth2, the orinoco device, no longer exists (it's not listed in /proc/net/dev).
Maciej Babinski
Quoted 4 lines · Maciej
I just switched from 2.5.68 to 2.5.70, and I'm having trouble removing the
orinoco_csmodule on the fly. After bringing the interface down, doing an "rmmodorinoco_cs" causes the rmmod process to lock up, and subseqeunt invocations of lsmod and 'cat/proc/modules' to do the
same.
Quoted 2 lines
I get a bunch of messages like the following in the kernel log:
"unregister_netdevice: waiting for eth2 to become free. Usage count =
1
Quoted 2 lines
However, eth2, the orinoco device, no longer exists (it's not listed in
/proc/net/dev).
i've seen this also with my orinoco_cs and my 3c574_cs.
Signature · 3 lines
____________________}John Flinchbaugh{______________________
| [email protected] http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~Quoted 10 lines · Maciej
I just switched from 2.5.68 to 2.5.70, and I'm having trouble removing the
orinoco_csmodule on the fly. After bringing the interface down, doing an "rmmodorinoco_cs" causes the rmmod process to lock up, and subseqeunt invocations of lsmod and 'cat/proc/modules' to do the same. I get a bunch of messages like the following in the kernel log:"
unregister_netdevice: waiting for eth2 to become free. Usage count = 1However, eth2, the orinoco device, no longer exists (it's not listed in
/proc/net/dev).
Yeah, that version of the driver is buggy. I've already sent an update to Linus, which is in current BK.
Signature · 4 lines
David Gibson | For every complex problem there is a [email protected] | solution which is simple, neat and | wrong. http://www.ozlabs.org/people/dgibson