netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org, waltje@uwalt.nl.mugnet.org,
	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: Wed, 06 Sep 2006 11:01:40 -0700	[thread overview]
Message-ID: <44FF0D04.5020405@candelatech.com> (raw)
In-Reply-To: <9a8748490609010435k6b327237ve6a23ddcaa0f4065@mail.gmail.com>

Jesper Juhl wrote:
> Ok, I've done some more testing and it seems, unfortunately, that I
> can't trigger the problem reliably. I guess I was just "lucky" with my
> first few reboots.
> It now seems that uptime and/or amount of data that has flowed over
> the vlan interface impacts the probability of hitting the problem.

Back when I was chasing the neighbor table leak, I wrote a patch to
catch ref-count leaks for net devices.  It was against 2.6.13 or so,
but if nothing else is helping, it might be worth dusting off.

I put what I believe was the last iteration of that patch here:

http://www.candelatech.com/oss/rfcnt.patch

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2006-09-06 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-31 15:17 Unable to halt or reboot due to - unregister_netdevice: waiting for eth0.20 to become free. Usage count = 1 Jesper Juhl
2006-08-31 15:30 ` Ben Greear
2006-08-31 15:33   ` Jesper Juhl
2006-09-01  9:59     ` Jesper Juhl
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 [this message]

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=44FF0D04.5020405@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jesper.juhl@gmail.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;
as well as URLs for NNTP newsgroup(s).