From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Ben Greear" <greearb@candelatech.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Fred N. van Kempen" <waltje@uwalt.nl.mugnet.org>,
"Ross Biro" <ross.biro@gmail.com>,
davem@davemloft.net, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org
Subject: Re: Unable to halt or reboot due to - unregister_netdevice: waiting for eth0.20 to become free. Usage count = 1
Date: Fri, 1 Sep 2006 11:59:44 +0200 [thread overview]
Message-ID: <9a8748490609010259l7c42ca88tbcc87410a770b48c@mail.gmail.com> (raw)
In-Reply-To: <9a8748490608310833x22b0ca30s2130cc388e2bb392@mail.gmail.com>
On 31/08/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 31/08/06, Ben Greear <greearb@candelatech.com> wrote:
> > Jesper Juhl wrote:
> > > Hi,
> > >
> > > I've got a small problem with 2.6.18-rc5-git2.
> > >
> > > I've got a vlan setup on eth0.20, eth0 does not have an IP.
> > >
> > > When I attempt to reboot or halt the machine I get the following
> > > message from the loop in net/core/dev.c::netdev_wait_allrefs() where
> > > it waits for the ref-count to drop to zero.
> > > Unfortunately the ref-count stays at 1 forever and the server never
> > > gets any further.
> > >
> > > unregister_netdevice: waiting for eth0.20 to become free. Usage count = 1
> > >
> > > I googled a bit and found that people have had similar problems in the
> > > past and could work around them by shutting down the vlan interface
> > > before the 'lo' interface. I tried that and indeed, it works.
> > >
> > > Any idea how we can get this fixed?
> >
> > This is usually a ref-count leak somewhere. Used to be IPv6 had
> > issues..then there were some neighbor leaks...but these were fixed as
> > far as I know.
> >
> Using IPv4 here.
>
>
> > Can you reproduce this on older kernels?
> >
> I've not actively tried, but I do have several servers running various
> older kernel releases with similar vlan setups and I'm not aware of
> any problems with those. Only this new box that I'm using for testing
> new kernels (currently) shows the problem, and I've only tried 2.6.8
> and 2.6.18-rc5-git2 on the box so far (2.6.8 doesn't have the
> problem).
>
I've just encountered the problem on a different server with an
identical vlan setup. That server is running 2.6.13.4
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-09-01 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 15:17 Jesper Juhl
2006-08-31 15:30 ` Ben Greear
2006-08-31 15:33 ` Jesper Juhl
2006-09-01 9:59 ` Jesper Juhl [this message]
2006-09-01 10:41 ` Herbert Xu
2006-09-01 10:51 ` Jesper Juhl
2006-09-01 11:35 ` Jesper Juhl
2006-09-06 18:01 ` Ben Greear
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=9a8748490609010259l7c42ca88tbcc87410a770b48c@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ross.biro@gmail.com \
--cc=waltje@uwalt.nl.mugnet.org \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®