Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Robert Scott <rbscott@axentra.net>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] unregister_netdevice: waiting for br0 to become free. Usage count = 1 (2.6.12.3)
Date: Wed, 31 Aug 2005 21:37:49 -0700	[thread overview]
Message-ID: <20050831213749.6bc8dd50@localhost.localdomain> (raw)
In-Reply-To: <8189B9F5-DF6E-4032-8D2D-D5301A02A081@axentra.net>

On Wed, 31 Aug 2005 19:04:01 -0700
Robert Scott <rbscott@axentra.net> wrote:

> Hello,
> 
> I know that this bug has been discussed before at length on this  
> mailing list, but previous post seemed to indicate that it was fixed  
> before kernel 2.6.12.  I am still seeing this occasionally in kernel  
> 2.6.12.3.  The system is running knoppix, and IPV6 is not compiled  
> into the kernel(other posts mentioned numerous problems with the IPV6  
> code).  But every so often, when bringing down the bridge (it doesn't  
> happen every time), the process hangs, and the following message  
> appears in dmesg repeatedly:
> 
> 'unregister_netdevice: waiting for br0 to become free. Usage count = 1'
> 
> None of the processes involved can be killed, and an attempt to run  
> an ifconfig results in a process that is also waiting forever.  At  
> this point the box must be rebooted forcefully.
> 
> Two questions.
> 1. In a previous post, someone mentioned one solution was to  
> commenting out the check that is hanging in the kernel.   Does this  
> check preventing something terrible from happening(i assumed that it  
> does), or is it safe to remove it

Really bad idea, because if the thing that is holding the reference
like packets stuck in some dead queue, ever get processed the kernel
will die.

> 2. Any ideas of something to try in order to make this repeatable?

Two other recent reports are:
1. Buggy applications that hold packets in their input queue forever,
   and/or netfilters.  The socket buffer's contain a reference for
   packets in flight.

2. The VLAN code had a number of reference bugs, if you look through
   recent netdev mailing list you will see the discussion.

  parent reply	other threads:[~2005-09-01  4:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01  2:04 [Bridge] unregister_netdevice: waiting for br0 to become free. Usage count = 1 (2.6.12.3) Robert Scott
2005-09-01  4:26 ` Ben Greear
2005-09-01  4:37 ` Stephen Hemminger [this message]
2005-09-01  5:12   ` Ben Greear
2005-09-01  6:33   ` Robert Scott
2005-09-01 16:24     ` Stephen Hemminger
2005-09-01 19:04   ` Patrick McHardy
  -- strict thread matches above, loose matches on Subject: below --
2005-09-02  7:37 Louis Croisez
2015-06-26 12:04 Jorge Dominguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050831213749.6bc8dd50@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=bridge@lists.osdl.org \
    --cc=rbscott@axentra.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox