This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: mininet (Ubuntu)
Importance: Undecided => Medium
--
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 notificat
It has shown up multiple times in our (mininet) nightly tests on 13.10
beta, but I don't know if it is still being seen on the Ubuntu testing
side.
Sent from my iPhone
On Oct 10, 2013, at 1:12 PM, Joseph Salisbury
wrote:
> @James Page, are you seeing this bug again, or are you still unable to
>
@James Page, are you seeing this bug again, or are you still unable to
reproduce it?
--
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
T
I'm still seeing this in 13.10 beta.
--
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:
htt
[ 2091.229234] unregister_netdevice: waiting for lo to become free. Usage count
= 3
[ 2101.338376] unregister_netdevice: waiting for lo to become free. Usage count
= 3
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a m
I'm still seeing this in 12.04.3.
--
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:
Given the number of bugs that the Kernel Team receives during any
development cycle it is impossible for us to review them all. Therefore,
we occasionally resort to using automated bots to request further
testing. This is such a request.
We are approaching release and would like to confirm if this
i have to revoke my previous statement: the bridge only makes the bug to
appear less frequent.
--
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 co
one small (and maybe weird) addition to my last post:
Whenever a system is configured with a bridge, the error seems NOT to occur. In
our lab we have 4 systems, two with configured bridges and two without. Only
the systems without bridges behave erroneous.
If, after a reboot, a bridge is added t
I am able to reproduce this bug with both kernel versions
Linux fgcn-of-4 3.11.0-5-generic #11-Ubuntu SMP Fri Sep 6 19:01:31 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Linux fgcn-of-3 3.11.0-031100-generic #201309021735 SMP Mon Sep 2 21:36:21 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
i am using the f
@Joseph
I'm unable to reproduce this issue on the latest saucy kernel - did you
manage to ID which commit fixed this up? I'm concerned it exists in
other kernel versions 12.04->13.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Comment #35 inb bug 1181315 suggests that bug may be resolved in
3.10.0.2. Can you test that kernel and see if it still exhibits the
bug?
--
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:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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 notificatio
i am really not an kernel expert but i found that some kernel helper
process hangs in line 283 of net/core/net_namespace.c (kernel version
3.2)
281 /* Run all of the network namespace exit methods */
282 list_for_each_entry_reverse(ops, &pernet_list, list)
283 ops_exit_list
This looks very much like bug 1181315
--
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:
ht
I'm not sure if this information is helpful, but i am seeing the process
(mnexec) hanging in a kernel-call.
# uname -a
Linux fgcn-of-3 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux
this is a snippet from my syslog:
Jul 9 15:43:25 fgcn-of-3 kernel: [11261.060357] unregister_netdevice:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mininet (Ubuntu)
Status: New => Confirmed
--
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:
mi
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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
apport information
** Tags added: apport-collected
** Description changed:
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
Note that this has been seen on 12.04.2 systems running the 3.5 kernel
and on the 3.10 kernel in Saucy.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
21 matches
Mail list logo
