The group I work with has seen that, or something similar, in a test lab environment. It seems unrelated to what type of underlying device (kernel bonding, brand or speed of physical adapter, etc...), how it was created and how it was removed (vconfig rem, rmmod, etc...) The only (slightly educated) guess we have is that it is somehow related to uptime and / or load as when it appears it is usually during stress tests run overnight or over the weekend. We noticed that when this appears the (incorrect?) reference count is always 3. Also, I am not sure that removing the VLAN interface while the interface is up is necessarily a factor here as: - We often do that without seeing any problems (yeah I know that's probably not a good practice, but it's a test lab ;-) - I am pretty sure (but not absolutely positive) we have seen this occur when we have brought the VLAN interface down properly before removing it. While my group is a test lab, we are not really testing 8021q, but it is used in some of our test configurations. We are usually using either the distributions kernel (mostly Red Hat 4, Fedora, SuSE SLES 9 and/or SuSE Pro 9.x) or the latest 2.6 kernel. And of course, Intel requires that I make a disclaimer that my views and opinions are mine and do not necessarily represent the company... -Aaron -----Original Message----- From: vlan-bounces@xxxxxxxxxxxxxxx [mailto:vlan-bounces@xxxxxxxxxxxxxxx] On Behalf Of Rezwanul_Kabir@xxxxxxxx Sent: Tuesday, April 19, 2005 11:07 AM To: vlan@xxxxxxxxxxxxxxx Subject: RE: [VLAN] Failure Removing 8021q VLAN Interface I am not trying to unload the 8021q module. Just trying to do "vconfig rem ethX.X" to remove the VLAN interface causes the failure.. Thanks.. --rez > -----Original Message----- > From: vlan-bounces@xxxxxxxxxxxxxxx > [mailto:vlan-bounces@xxxxxxxxxxxxxxx]On Behalf Of Peter Stuge > Sent: Tuesday, April 19, 2005 1:01 PM > To: vlan@xxxxxxxxxxxxxxx > Subject: Re: [VLAN] Failure Removing 8021q VLAN Interface > > > On Tue, Apr 19, 2005 at 12:08:12PM -0500, > Rezwanul_Kabir@xxxxxxxx wrote: > > The issue is as below: > > An attempt to remove an 802.1q VLAN frequently results in > > failure. The problem can occur both when manually removing the > > interface and when shutting down the operating system. When the > > failure occurs, a message similar to the following is repeatedly > > printed to the console approximately every ten seconds. > > > > unregister_netdevice: waiting for eth0.10 to become free. > > Usage count = 3 > > I'm guessing that the module doesn't want to unload unless all VLAN > interfaces are downed and vconfig rem:d first. > > > //Peter > _______________________________________________ > Vlan mailing list > Vlan@xxxxxxxxxxxxxxx > http://www.lanforge.com/mailman/listinfo/vlan > _______________________________________________ Vlan mailing list Vlan@xxxxxxxxxxxxxxx http://www.lanforge.com/mailman/listinfo/vlan
