All of lore.kernel.org
 help / color / mirror / Atom feed
From: Louis Croisez <louis.croisez@gmail.com>
To: bridge@lists.osdl.org, rbscott@axentra.net
Subject: [Bridge] unregister_netdevice: waiting for br0 to become free. Usage count = 1 (2.6.12.3)
Date: Fri, 2 Sep 2005 09:37:31 +0200	[thread overview]
Message-ID: <34d8b2fe05090200376d8182ce@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2032 bytes --]

Hi Robert,

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

What i would do to reproduce it, is make a script establishing the bridge, 
then flooding the bridge with some external ping -f, then shuting down the 
bridge. If there is a refcount release problem, it should appear on eavy 
load (some buffer overflow, or something like that).
Also, are you playing with ebtables? How do you use this bridge?
#Louis.


Date: Wed, 31 Aug 2005 19:04:01 -0700
> From: Robert Scott <rbscott@axentra.net>
> Subject: [Bridge] unregister_netdevice: waiting for br0 to become
> free. Usage count = 1 (2.6.12.3 <http://2.6.12.3/>)
> To: bridge@lists.osdl.org
> Message-ID: <8189B9F5-DF6E-4032-8D2D-D5301A02A081@axentra.net>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
> 
> 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 <http://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.
> 2. Any ideas of something to try in order to make this repeatable?
> 
> thanks,
> --robert scott

[-- Attachment #2: Type: text/html, Size: 3078 bytes --]

             reply	other threads:[~2005-09-02  7:37 UTC|newest]

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

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=34d8b2fe05090200376d8182ce@mail.gmail.com \
    --to=louis.croisez@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.