From: Andre Tomt <andre@tomt.net>
To: Netdev <netdev@oss.sgi.com>
Subject: 2.6.10 vlan stuck on vconfig on interface removal
Date: Mon, 10 Jan 2005 06:10:44 +0100 [thread overview]
Message-ID: <41E20E54.5030008@tomt.net> (raw)
Hi!
Another "unregister_netdevice: waiting for eth0.1 to become free. Usage
count = 1" issue coming up.. Fun fun fun! And this one also seems to be
related to the ipv6 stack.
I can reproduce this reliably this by ifdown lo before ifdown'ing
eth0.1. That is, if lo goes down first, vconfig rem eth0.1 gets stuck
when run later. This only happens with ipv6.ko loaded. I havn't added
*any* ipv6 adresses to any interace, the only one are those the
ipv6-stack adds itself.
This is hitting us often on our routers, as we have ipv6.ko loaded, and
Debian runs ifdown -a (bring down all configured interfaces, starting
with lo unfortunatly) on shutdown and reboot.
Bringing down non-vlan interfaces works just fine after killing lo.
a backtrace from vconfing captured with sysrq-T (quickly typed off-screen):
shedule_timeout
process_timeout
netdev_wait_allrefs
netdev_wait_allrefs
netdev_run_todo
unregister_vlan_device [8021q]
vlan_ioctl_handler [8021q]
sock_ioctl
sys_ioctl
syscall_call
The lab machine is running with a minimalist config, no listeners
besides sshd, ipv6.ko and 8021q.ko loaded.
reply other threads:[~2005-01-10 5:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41E20E54.5030008@tomt.net \
--to=andre@tomt.net \
--cc=netdev@oss.sgi.com \
/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).