lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a8748490608310817v7d722f88u167b5a84d0ff67e8@mail.gmail.com>
Date:	Thu, 31 Aug 2006 17:17:20 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Cc:	"Mark Evans" <evansmp@...ra.aston.ac.uk>,
	"Fred N. van Kempen" <waltje@...lt.NL.Mugnet.ORG>,
	"Ross Biro" <ross.biro@...il.com>, davem@...emloft.net,
	yoshfuji@...ux-ipv6.org, "Ben Greear" <greearb@...delatech.com>,
	netdev@...r.kernel.org
Subject: Unable to halt or reboot due to - unregister_netdevice: waiting for eth0.20 to become free. Usage count = 1

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?


-- 
Jesper Juhl <jesper.juhl@...il.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ