Dear Ben ,
I had this problem also on bond0 device which is eth0 and eth1 bonded
device. I thought that it might cause of bonding and that's why I didn't
report it before . But the message is as same as darkstar reported.
---
Regards
=================================================================
/ Seyyed Hamid Reza / WINDOWS FOR NOW !! /
/ Hashemi Golpayegani / Linux for future , FreeBSD for ever /
/ Morva System Co. / ------------------------------------- /
/ Network Administrator/ hamid@xxxxxxxxx , ICQ# : 42209876 /
================================================================
-----Original Message-----
From: vlan-bounces@xxxxxxxxxxxxxxx [mailto:vlan-bounces@xxxxxxxxxxxxxxx] On
Behalf Of Ben Greear
Sent: Thursday, July 21, 2005 9:21 PM
To: Linux 802.1Q VLAN
Subject: Re: [VLAN] unregister_netdevice
darkstar wrote:
> After all these procedures systems hangs and I was reeboot it.
> I hope this information will be useful.
Well, I still don't know what is holding the reference. I don't think this
is a bug in VLAN code itself, because otherwise lots of people would be
reporting it.
The only thing I can suggest is to try various different things, including
never loading iptables in the first place, and see if you can find the step
that causes the problem.
If you can find the module that is holding the reference, a bug report can
be sent to that module's author.
One other thing: Have you tried specifically dropping each VLAN interface
before unloading the module: ifconfig ethX.foo down
That might possibly help trigger other code to release the reference.
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
Vlan mailing list
Vlan@xxxxxxxxxxxxxxx
http://www.lanforge.com/mailman/listinfo/vlan
