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
On Wed, Jun 04, 2003 at 12:51:21PM -0500, Maciej wrote:
> 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).
i've seen this also with my orinoco_cs and my 3c574_cs.
--
____________________}John Flinchbaugh{______________________
| [email protected] http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
On Wed, Jun 04, 2003 at 12:51:21PM -0500, Maciej wrote:
> 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).
Yeah, that version of the driver is buggy. I've already sent an
update to Linus, which is in current BK.
--
David Gibson | For every complex problem there is a
[email protected] | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson