** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in Linux:
I've got this issue on
```
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
# uname -a
Linux ultima 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
```
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in Linux:
** Changed in: linux-lts-xenial (Ubuntu Trusty)
Status: Confirmed => Won't Fix
** Changed in: linux-lts-utopic (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux-lts-xenial (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you
** Changed in: linux
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free.
Launchpad has imported 18 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=81211.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Since this bug has been long-since marked 'fix released', I opened a new
bug 1711407. Let's all please use that one for continued discussion of
this problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
I've hit the same issue today with 4.4.0-87-generic on a xenial.
Is there a confirmed fix for a particular released kernel for Ubuntu?
And same for 4.10.0-28-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in
I've hit the same issue today with 4.4.0-87-generic on a xenial.
Is there a confirmed fix for a particular released kernel for Ubuntu?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
I added the 2 commits referenced in the docker thread:
https://github.com/docker/docker/issues/5618#issuecomment-262081488
which is building right now in the test ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1403152
kernel version 4.4.0-53.74+hf1403152v20161214b1 is the latest xenial
I reproduce the problem with LXC 2.0.6-1 and kernel 4.6.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free.
Seems like the fix isn't in or isn't working for this problem as I've just hit
this issue again on 4.4.0-49, at least twice:
[434074.636075] unregister_netdevice: waiting for lo to become free. Usage
count = 1
Since, I see a lot of people talking about 4.8+ kernels fixing this issue, is
there
Update:
I've hit the issue with 4.4.0-47... now testing 4.4.0-49 for the next weeks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice:
Dear Dan, user reshen on the github Docker issue thread [1] did some
extensive testing using kernel 4.8.8. He has not been able to reproduce
the issue using that version. I've also done testing using the ubuntu
mainline kernel builds and also not been able to reproduce the issue
anymore.
He has
seeing this on xenial after this sequence of operations:
lxc stop run2
lxc delete run2
lxc copy run1 run2
lxc start run2 <- hangs here, with later dmesg
[337766.146479] unregister_netdevice: waiting for lo to become free. Usage
count = 1
[337772.435786] INFO: task lxd:20665 blocked for more
I was running 4.4.0-46 (not sure if different than the latest .67?) on
October 27th and yesterday had to reboot for the "... count = 1"
problem.
Was there previous 4.4.0-46 releases? If not, the bug is still
present...
Otherwise, I'll confirm if it happens again, or if it doesn't within a
few
> From the logs it looks like the patch is now a part of
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627730 which hit
> 4.4.0-46.67~14.04.1
> (proposed) on 22nd Oct?
yes, the patch is included in the 4.4.0-46.67 kernel (both linux-lts-
xenial on trusty, and regular linux on xenial).
>From the logs it looks like the patch is now a part of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627730 which hit
4.4.0-46.67~14.04.1 (proposed) on 22nd Oct?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in
> Well, if that made it into Ubuntu's kernel before and including 4.4.0-42, it
> didn't fix it
> (I still get the bug on many machines & VMs).
No, it's not in the released xenial kernel yet, the upstream 4.4.22
stable commits are still in the xenial master-next branch kernel; it'll
be a bit
Oh oops, didn't realize this was the patch with the
751eb6b6042a596b0080967c1a529a9fe98dac1d commit Paul mentionned.
Well, if that made it into Ubuntu's kernel before and including
4.4.0-42, it didn't fix it (I still get the bug on many machines & VMs).
--
You received this bug notification
> Apparently the fix is in:
>
> https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.22
Hopefully the commit does fix things, although Paul's comment above
indicated it may not, at least not for everyone.
--
You received this bug notification because you are a member of Kernel
Packages,
Apparently the fix is in:
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.22
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice:
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in
> I've tried your PPA with the included patch (4.4.0-36-generic
> #55hf1403152v20160916b1-Ubuntu).
> As I've also reported on the Github docker issue [1], this does not fix the
> issue for me.
that's unfortunate.
> Would it help you test again with this patch, and with your debug
patches
Dan, thanks for your work. I've tried your PPA with the included patch
(4.4.0-36-generic #55hf1403152v20160916b1-Ubuntu). As I've also reported
on the Github docker issue [1], this does not fix the issue for me.
Would it help you test again with this patch, and with your debug
patches included?
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-xenial (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-xenial (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
PPA updated with patched test kernels for xenial as well as trusty lts-xenial.
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1403152
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
Ah, you need a patched test kernel on xenial...I'll upload one to the
PPA for testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice:
Alexandre, please see my last comment, that links to a test kernel PPA
with EXACTLY that upstream commit,
751eb6b6042a596b0080967c1a529a9fe98dac1d ("ipv6: addrconf: fix dev
refcont leak when DAD failed")
If you can reproduce this, please test with the PPA and report if it
fixes the problem.
--
Bug was reintroduced in Ubuntu Xenial's kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
This kernel bug, is affecting all the container solutions also on Xenial
/ 16.04.1 up to 4.4.0-38.
Lots of people are hitting this on many distributions / container solutions:
https://github.com/docker/docker/issues/5618 (mentions Docker, LXC, kubernetes,
etc.)
** Also affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice:
There are upstream commits that may fix this problem, I've updated the same ppa
with a new test build (with only the commits, and without any debug). If
anyone can still reproduce this problem, please try the latest kernel in the
ppa and report if it fixes the problem or not:
Credit where credit is due: we've slowly rolled the patch above (per
#63) into production over the last six months, initially through custom
compiled kernels and more recently via mainline LTS wily packages; and
have seen no further issues with hung namespaces. Kudos to ddstreet.
--
You
If anyone is able to reproduce this, I have a debug kernel at this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1403152
it prints a debug line when any loopback interface is dev_put/dev_hold,
which may help show where the extra loopback reference is coming from
when this problem
Cristian ok thnx. I'll keep investigating.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
@ddstreet, the Ubuntu-lts-3.19.0-49.55_14.04.1 doesn't seem to fix this issue.
We just upgraded a Juno openstack environment to this kernel version and we are
still seeing this on a network node.
[controller] root@node-28:~# uname -a
Linux node-28.domain.tld 3.19.0-49-generic #55~14.04.1-Ubuntu
I should note that I'm pretty sure this new problem is almost certainly
a different bug (different cause) than the original bug fixed in comment
59 and earlier; just the symptoms appear the same.
--
You received this bug notification because you are a member of Kernel
Packages, which is
> James Dempsey, the upstream commit you referenced is in trusty lts-
vivid at Ubuntu-lts-3.19.0-49.55_14.04.1
specifically, upstream it's commit
30f7ea1c2b5f5fb7462c5ae44fe2e40cb2d6a474 and in the trusty lts branch
it's commit a8412804321b96aac2665527535ac28a934ed0e2
--
You received this bug
Andrew Ruthven that's your patch also ^
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status
Rodrigo, just in case the problem you're seeing is fixed by ^ commit,
please try the latest trusty lts-vivid (at version I listed above, or
later).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
James Dempsey, the upstream commit you referenced is in trusty lts-vivid
at Ubuntu-lts-3.19.0-49.55_14.04.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
** Changed in: linux-lts-utopic (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo
Andrew, Rodrigo, James, do any of you have a crash dump from a system
where the problem has happened? or any way to more easily reproduce it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
FWIW here is an update of what I've tried in the last couple months
trying to fix this problem (unsuccessfully):
- We tried to deny packets to the container's network before we destroy the
namesapce
- Backported the patch mentioned in the previous comment to ubuntu kernel 3.19
and 4.2
We also backported [1] to 4.2 (linux-lts-wily) and deployed it to our
production OpenStack cloud. We just installed it yesterday and our MTBF
is between two and twenty days, so we won't know if this has made any
difference for a while now.
Some details about our configuration / failure mode:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
We're still seeing the same issue on Ubuntu Trusty running the linux-
image-3.19.0-30-generic kernel.
Looking at this thread[0] on the Docker site which is referenced to in
the kernel bugzilla for this issue, there is a reference[1] to a
patch[2] on the netdev mailing list from 2015-11-05 by
** Changed in: linux (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to
This bug was fixed in the package linux-lts-utopic -
3.16.0-46.62~14.04.1
---
linux-lts-utopic (3.16.0-46.62~14.04.1) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1483790
* SAUCE: REBASE-FIXUP: debian/scripts/misc/getabis: fix abi directory
[
This bug was fixed in the package linux - 3.19.0-26.28
---
linux (3.19.0-26.28) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1483630
[ Upstream Kernel Changes ]
* Revert Bluetooth: ath3k: Add support of 04ca:300d AR3012 device
linux
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-vivid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage
Chris, I will start testing this build and let you know how it goes.
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to
What is the patch?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in Linux:
Unknown
Status in
Dave,
I added it to the description of the bug:
commit de84d89030fa4efa44c02c96c8b4a8176042c4ff
--chris
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) = (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Trusty)
Status: In Progress = Fix Committed
** Changed in: linux (Ubuntu Utopic)
Status: In Progress = Fix Committed
** Changed in: linux (Ubuntu Vivid)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a
Ok so I have reports that NFS may also be a red herring, however I've
found a patch that seems to greatly mitigate issues when testing with
the reproducer I was provided. So I'm going to provide a test build with
that for 3.13, 3.16, 3.19 and users can give me feedback if that helps.
In addition,
Build is here:
http://people.canonical.com/~arges/lp1403152/
Please test and give feedback. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice:
So it seems like disabling CONFIG_BRIDGE_NETFILTER is a red herring,
I've been able to reproduce with this off as well on 3.19.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Looks like no progress on the netdev side yet?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in
I can confirm that disabling CONFIG_BRIDGE_NETFILTER and/or disabling
net.bridge.bridge-nf-call-iptables makes me unable to repro on Ubuntu
14.04 running 3.13.0-53-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Email sent to netdev about what we've found so far with this bug:
http://www.spinics.net/lists/netdev/msg333868.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
A summary of the bug so far:
Occasionally starting and stopping many containers with network traffic may
result in new containers being unable to start due to the inability to create
new network namespaces.
The following message repeats in the kernel log until reboot.
unregister_netdevice:
Joe,
I've created bug 1466135 to handle updating our 3.13 to fix your issue. Please
add any information to that bug that would be useful in verifying the fix once
it goes through our stable updates process. Thanks!
--
You received this bug notification because you are a member of Kernel
Steve saw this patch: e53376bef2cd97d3e3f61fdc677fb8da7d03d0da as a
potential fix. For completeness I tested a backport to 3.13 (since its
in 3.14+). The same failure mode occurs with this patch.
Disabling sysctl_ip_early_demux still causes a failure.
To work around this issue, if you don't need
Just chiming in here, I contacted Rodrigo off-list and was verging
towards that same patch. More below.
I suspect there's two issues here with very similar symptoms. In
particular post #8 which mentions people reporting that 3.14 improves
the situation.
Really great progress! Sounds like you're close to finding a fix.
Thanks Chris.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to
A few more results:
- I can track the dst_entry holding the dev causing the issue.
- I can reproduce on v3.19 kernels by first using 'modprobe br_netfilter'.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Additional Experiments:
- No NAT, lxc bridges to VM eth0, which is bridged to host machine br0
Still fails
- Let timeout on unregister_notifier keep going
Still running after an hour, can't create new containers (original
issue)
sudo conntrack -{L,F} hangs...
- Purge
When running the reproducer, if I mount the nfs drive using -o
vers=3,proto=udp (udp instead of tcp), I cannot get any failures when
running 10 threads 150 iterations multiple times.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Dave,
Working on this now. I tried a bisect between v3.12..v3.13 where it seemed that
3.12 worked better, but it wasn't conclusive. I tried looking at dev_put
dev_hold via systemtap, but that seems to modify the timing sufficiently.
Looking at comments from Jordan Curzon to see if I can start
Sounds good, thanks Chris.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in The Linux Kernel:
Any updates?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in The Linux Kernel:
Unknown
Status
Great progress, thanks Chris. I did some initial instrumentation of
dev_put and dev_hold calls earlier, dumping out the call stack and
comparing a good run to a bad one. Nothing definitive yet, and it's bit
tricky to match up on an SMP machine, but one thing stood out: many of
the bad traces had
The result of the reverse bisect between v3.17..v3.18 with the reproducer was:
# first bad commit: [34666d467cbf1e2e3c7bb15a63eccfb582cdd71f] netfilter:
bridge: move br_netfilter out of the core
If I backport this patch plus 7276ca3f on top of v3.17 I no longer get the hang
with the simple
It happens to me on Centos 7, with kernel 4.0.1-1.el7.elrepo.x86_64
Every time I reboot a container, without any particular heavy data load, I ge
[630362.513630] hrtimer: interrupt took 5912836 ns
[727851.858312] device eth0 left promiscuous mode
[727853.622084] eth0: renamed from mcCDGW73
This is fixed in v3.18 and broken in v3.17. Doing a reverse bisect on
this to determine which patch(es) fix this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
Ok. For what it's worth, we still see the problem on Ubuntu 15.04
running v3.19. However, the problem is much harder to trigger and the
attached reproducer script does not trigger the problem there, so I
don't have code to reliably repro it on 3.19.
--
You received this bug notification
Dave,
Good to know. Hopefully the bisect will implicate the right lines of code in
order to find a v3.19+ fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
Agreed. Thanks for pushing this forward Chris.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in
Great, thanks Chris! Let me know if I can help further.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Ok, moved to two real machines and I can repro there:
[ 3797.901145] unregister_netdevice: waiting for lo to become free. Usage count
= 1
Will continue to look at this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: Stefan Bader (smb) = Chris J Arges (arges)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for
So far I haven't been able to reproduce this with 3.13.0-49, nor
3.13.0-37.
My setup is as follows:
Two vms, one with nfs-server and another for reproducer.
nfs-server setup with these commands:
apt-get install nfs-kernel-server
mkdir /export
chown 777 /export
echo /export
Here's the setup I use: run the reproducer in a 14.04 server VM (Linux
ubuntu 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux), VM is bridged to host machine's en0. I
am using VMware Fusion on OSX 10.10 host.
Containers inside the VM use NAT via lxcbr0
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free.
Ok, I've got a minimal reproducer ready. It causes the bug when I run
it on Ubuntu 14.04 with 3.13.0-24-generic and LXC version
1.0.7-0ubuntu0.1 0. It's python, and the script has some documentation
describing its usage as well as the prerequisites. You should run it as
root via sudo.
Prereqs
David, would you like help getting the reproducer code ready to share?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free.
I am able to reliably recreate this on both Ubuntu 14.04 with kernel
3.13.0-37-generic and Ubuntu 14.10 with kernel 3.16.0-23-generic. I
have test code that can hit the bug, but it's not cleaned up enough to
share. The steps to repro are:
Start a container (COW clone using overlayfs from a
An addition to my #18 comment above. I forgot that I had to remove
logging on calls from skb_release_head_state to dst_release due to
performance impact of the number of calls. In both failure and success
scenarios, calls to dst_release by skb_release_head_state are also
present.
--
You received
Answering for Jordan
# uname -a
Linux ip-10-30-153-210 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
# dpkg -l | grep linux
ii libselinux1:amd642.2.2-1ubuntu0.1 amd64
SELinux runtime shared libraries
ii
Jordan, which kernel version are you using to make your observations
(thanks a lot for those, btw).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice:
To add to my comment just above, we have found a workload that is not
under own our control (which limits what we can do with it, including
sharing it) but which exacerbates the issue on our systems. This
workload causes the issue less than 5% of the time and that gives us the
chance to look at
I'm working with Rodrigo Vaz and we've found some details about our
occurrence of this issue using systemtap.
rt_cache_route places a dst_entry struct into a fib_nh struct as the
nh_rth_input. Occasionally the reference counter on that dst is not
decremented by the time free_fib_info_rcu is
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) = Stefan Bader (smb)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Utopic)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 116 matches
Mail list logo
