netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Roland" <devzero@web.de>
To: "\"Andrew Morton\"" <akpm@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
	"Jonathan Naylor" <g4klx@g4klx.demon.co.uk>
Subject: Re: 24rc8: unregister_netdevice: waiting for ... to become free
Date: Fri, 2 May 2008 14:38:36 +0200	[thread overview]
Message-ID: <008f01c8ac51$83dbd5d0$6400a8c0@bui.materna.com> (raw)

>> > i`m also seeing this one, but with pcnet32 - "modprobe -r pcnet32" 
>> > never
>> > returns and
>> >
>> > "unregister_netdevice: waiting for eth0 to become free. Usage count = 
>> > 1"
>> >
>> > being printed over and over again
>> >
>> > lsmod |grep pcnet32 shows
>> >
>> > pcnet32            35828    0
>> > mii                      9344    1    pcnet32
>> >
>> > i see stale ssh connection on port 22 and sshd for that session remains
>> > unkillable process.
>> >
>>
>> here a bug

it seems it`s lapbether driver

reproduce:

on system with pcnet32 (vmware) do

modprobe pcnet32
modprobe lapbether
modprobe -r lapbether
modprobe -r pcnet32 -> hang -> unregister_netdevice: waiting for eth0 to 
become free

didn`t try with other nic`s, but i assume it`s independent from pcnet32

MODULE_AUTHOR("Jonathan Naylor <g4klx@g4klx.demon.co.uk>");
MODULE_DESCRIPTION("The unofficial LAPB over Ethernet driver");
MODULE_LICENSE("GPL");

ok, experimental one, so not a real problem, but CC`ing  the Author.

regards
roland



----- Original Message ----- 
From: "Roland" <devzero@web.de>
To: ""Soeren Sonnenburg"" <kernel@nn7.de>
Cc: <linux-kernel@vger.kernel.org>; <netdev@vger.kernel.org>; ""Andrew 
Morton"" <akpm@linux-foundation.org>
Sent: Friday, May 02, 2008 11:31 AM
Subject: Re: 24rc8: unregister_netdevice: waiting for ... to become free


> >I am not exactly sure which kernel version Roland (?) is/was using but
>>from what I can tell this bug is fixed since 2.6.24 (at least). Well I
>>didn't see it with madwifi nor with the tun devices anymore on any of
>>the 24.X or 25rc's/25 ...
>
> pardon,   2.6.25-git17 in vmware
>
>
>>; <netdev@vger.kernel.org>;
> List:       linux-kernel
> Subject:    Re: 24rc8: unregister_netdevice: waiting for ... to become 
> free.
> From:       Soeren Sonnenburg <kernel () nn7 ! de>
> Date:       2008-05-02 6:15:43
> Message-ID: 1209708943.23075.52.camel () localhost
> [Download message RAW]
>
> On Thu, 2008-05-01 at 22:59 -0700, Andrew Morton wrote:
>> On Fri, 2 May 2008 03:26:28 +0200 "Roland" <devzero@web.de> wrote:
>>
>> > i`m also seeing this one, but with pcnet32 - "modprobe -r pcnet32" 
>> > never
>> > returns and
>> >
>> > "unregister_netdevice: waiting for eth0 to become free. Usage count = 
>> > 1"
>> >
>> > being printed over and over again
>> >
>> > lsmod |grep pcnet32 shows
>> >
>> > pcnet32            35828    0
>> > mii                      9344    1    pcnet32
>> >
>> > i see stale ssh connection on port 22 and sshd for that session remains
>> > unkillable process.
>> >
>>
>> here a bug
>>
>> >
>> >
>> > List:       linux-kernel
>> > Subject:    Re: 24rc8: unregister_netdevice: waiting for ... to become 
>> > free.
>> > From:       Soeren Sonnenburg <kernel () nn7 ! de>
>> > Date:       2008-01-29 8:59:10
>> > Message-ID: 1201597150.4973.10.camel () localhost
>> > [Download message RAW]
>> >
>> > On Tue, 2008-01-22 at 22:44 -0800, David Miller wrote:
>> > > From: Soeren Sonnenburg <kernel@nn7.de>
>> > > Date: Wed, 23 Jan 2008 07:42:21 +0100
>> > >
>> > > > Dear all,
>> > > >
>> > > > since some 2.6.24rc version I suddenly experience such messages on
>> > > > console when trying to shutdown a vpn connection:
>> > > >
>> > > > unregister_netdevice: waiting for tun0 to become free. Usage count 
>> > > > = 1
>> > > >
>> > > > or when removing an usb wlan dongle (although it was ifconfig wlan0
>> > > > down'd before)
>> > >
>> > > Current GIT already has a fix for this, attached below:
>> >
>> > hmmhhh, I am still seeing this problem on 2.6.24 with at least with the
>> > madwifi driver...
>> >
>> > Soeren
>>
>> there a bug.
>>
>>
>> Let's cc netdev@vger.kernel.org - linux-net is dead, afaik.
>>
>> Thanks for reporting all these bugs but please do take much mure care 
>> over
>> the cc's.  Be sure to cc every party who was cc'ed on the email to which
>> you're replying.  I restored Soeren.
>
> I am not exactly sure which kernel version Roland (?) is/was using but
> from what I can tell this bug is fixed since 2.6.24 (at least). Well I
> didn't see it with madwifi nor with the tun devices anymore on any of
> the 24.X or 25rc's/25 ...
>
> Soeren
> 


             reply	other threads:[~2008-05-02 12:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 12:38 Roland [this message]
2008-05-02 12:45 ` 24rc8: unregister_netdevice: waiting for ... to become free David Miller
2008-05-04  4:11   ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2008-05-04  9:33 devzero
2008-05-04 10:36 ` David Miller
2008-05-02  9:31 Roland
2008-05-02 15:57 ` Soeren Sonnenburg
2008-05-02 16:45   ` Roland
     [not found] <004701c8abf4$4cefe820$6400a8c0@bui.materna.com>
2008-05-02  5:59 ` Andrew Morton
2008-05-02  6:15   ` Soeren Sonnenburg

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='008f01c8ac51$83dbd5d0$6400a8c0@bui.materna.com' \
    --to=devzero@web.de \
    --cc=akpm@linux-foundation.org \
    --cc=g4klx@g4klx.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).