Public bug reported:

Raised upstream:

https://mailman.stanford.edu/pipermail/mininet-
discuss/2013-July/002473.html

Also seen in DEP-8 tests for Saucy:

https://jenkins.qa.ubuntu.com/job/saucy-adt-
openvswitch/28/ARCH=i386,label=adt/

Syslog extract:


Jul  1 10:57:42 autopkgtest ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl 
del-br s2
Jul  1 10:57:42 autopkgtest kernel: [  402.953438] device s2-eth3 left 
promiscuous mode
Jul  1 10:57:42 autopkgtest kernel: [  402.953588] device s2-eth4 left 
promiscuous mode
Jul  1 10:57:42 autopkgtest kernel: [  402.953724] device s2-eth7 left 
promiscuous mode
Jul  1 10:57:42 autopkgtest kernel: [  402.953853] device s2-eth6 left 
promiscuous mode
Jul  1 10:57:42 autopkgtest kernel: [  402.953986] device s2-eth2 left 
promiscuous mode
Jul  1 10:57:42 autopkgtest kernel: [  402.954049] device s2 left promiscuous 
mode
Jul  1 10:57:42 autopkgtest ovs-controller: 00366|poll_loop|DBG|wakeup due to 
[POLLIN] on fd 9 (127.0.0.1:6633<->127.0.0.1:40235) at ../lib/stream-fd.c:142 
(0% CPU usage)
Jul  1 10:57:42 autopkgtest ovs-controller: 
00367|rconn|DBG|tcp:127.0.0.1:40235: connection closed by peer
Jul  1 10:57:42 autopkgtest ovs-controller: 00368|rconn|DBG|void: entering VOID
Jul  1 10:57:42 autopkgtest ovs-controller: 00369|poll_loop|DBG|wakeup due to 
[POLLIN] on fd 6 (FIFO pipe:[44662]) at ../lib/fatal-signal.c:173 (0% CPU usage)
Jul  1 10:57:42 autopkgtest ovs-controller: 00370|fatal_signal|WARN|terminating 
with signal 15 (Terminated)
Jul  1 10:57:42 autopkgtest kernel: [  403.376840] IPv6: ADDRCONF(NETDEV_UP): 
s1-eth1: link is not ready
Jul  1 10:57:52 autopkgtest kernel: [  413.552113] unregister_netdevice: 
waiting for lo to become free. Usage count = 2
Jul  1 10:58:03 autopkgtest kernel: [  423.792110] unregister_netdevice: 
waiting for lo to become free. Usage count = 2
Jul  1 10:58:13 autopkgtest kernel: [  434.032116] unregister_netdevice: 
waiting for lo to become free. Usage count = 2
Jul  1 10:58:23 autopkgtest kernel: [  444.272126] unregister_netdevice: 
waiting for lo to become free. Usage count = 2

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: mininet 2.0.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Tue Jul  2 19:17:36 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-04-23 (70 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
MarkForUpload: True
SourcePackage: mininet
UpgradeStatus: Upgraded to saucy on 2013-06-15 (16 days ago)

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

** Affects: mininet (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug saucy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197078

Title:
  mininet created devices are not deleted correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197078/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to